djangoproject · Django · published 2026-10-06
CVE-2026-87975Privilege abuse in model formsets with editable primary keys
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-87975 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 13% of all CVEs. This Django vulnerability: CVSS 5.3 (v4.0). Fixed upstream in Django 6.1.2, 6.0.9, 5.2.18; patched packages are out for Debian; Debian and Ubuntu still have unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Django 6.1.2, 6.0.9, 5.2.18.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | python-django | No fix yet |
| 12 bookworm | python-django | Fixed in 3:3.2.25-0+deb12u6 | |
| Ubuntu | 26.04 LTS | python-django | No fix yet |
| 24.04 LTS | python-django | No fix yet | |
| 22.04 LTS | python-django | No fix yet |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Web frameworkDjango
Django security releases: 6.1.2, 6.0.9, 5.2.18
Upgrade to
6.1.26.0.95.2.18Why: CVE-2026-15307: EPSS 1.1% with high severity (CVSS 8.7).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (14th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.3 (v4.0)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- djangoproject Django
6.1to before6.1.2(affected)6.1.2(unaffected)6.0to before6.0.9(affected)6.0.9(unaffected)5.2to before5.2.18(affected)5.2.18(unaffected)
Description (from the CVE record)#
An issue was discovered in Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18. `django.forms.models.BaseModelFormSet.save_existing_objects()` used the presence of a primary key on a submitted form's instance as evidence that the instance belonged to the formset's limiting queryset. An object outside that queryset is represented by a newly constructed instance whose primary key can still be populated from submitted data when the model's primary key is a field accepted by the form, such as a `OneToOneField` or parent link used as the primary key of an inline formset's model, or a natural or UUID primary key included in the form's fields. This allows an authenticated user permitted to submit such a formset to delete rows outside the limiting queryset, without any permission on the targeted object, via forged management-form data marking an out-of-queryset object for deletion. Models using the default AutoField primary key are not affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Seonggwon Yoon for reporting this issue.
Quoted from the CVE Program record.