Quick answers
- Is CVE-2026-87975 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87975 being exploited in the wild.
- How severe is CVE-2026-87975?
- Medium severity, with a CVSS score of 4.3, published 6 October 2026.
- Which products and versions are affected?
- Django Software Foundation Django 6.1 before 6.1.2, 6.0 before 6.0.9, 5.2 before 5.2.18; unsupported series 5.1.x, 5.0.x, and 4.2.x may also be affected.
- Is there a fix for CVE-2026-87975?
- Yes: fixed in Django 6.1.2, 6.0.9, 5.2.18. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-87975 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-87975?
- Check whether you run Django Software Foundation Django at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Django 6.1.2, 6.0.9, 5.2.18
Technical details
The vulnerability exists in django.forms.models.BaseModelFormSet.save_existing_objects(), which improperly validates object ownership by trusting the presence of a primary key on form instances. When a model uses a primary key field accepted by the form (such as OneToOneField, parent link, natural key, or UUID primary key), an attacker can forge management-form data to mark out-of-queryset objects for deletion. Models using the default AutoField are not affected. The flaw requires authentication and form submission capability but no explicit permission on the targeted object.
Affected products
- Django Software Foundation Django 6.1 before 6.1.2, 6.0 before 6.0.9, 5.2 before 5.2.18; unsupported series 5.1.x, 5.0.x, and 4.2.x may also be affected
Timeline
- 2026-10-06: disclosed