CVE-2026-87975: djangoproject Django · Insecure Direct Object Reference
Affects djangoproject DjangoSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium · fixed in 6.1.2 : update djangoproject Django when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.1.2, 6.0.9, 5.2.18
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade Django and django to 6.1.2, 6.0.9 or 5.2.18.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| djangoprojectDjango | Affected
| Fixed in
|
| djangoprojectDjango | Affected
| Fixed in
|
| djangoprojectDjango | Affected
| Fixed in
|
PyPIdjangopkg:pypi/djangoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Django versions 6.1.2, 6.0.9, and 5.2.18. Users should upgrade to these or later versions to remediate the vulnerability. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-87975 is an authorization bypass vulnerability in Django affecting versions 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18. The issue arises in django.forms.models.BaseModelFormSet.save_existing_objects(), which incorrectly trusts the presence of a primary key on a submitted form's instance as proof that the instance belongs to the formset's limiting queryset. This flaw allows an authenticated user with permission to submit such a formset to delete objects outside the intended queryset by submitting forged management-form data. Models using the default AutoField primary key are not affected. The vulnerability has a medium severity with a CVSS score of 4.3.
References
- docs.djangoproject.com/en/dev/releases/security/ (opens in a new tab)
- groups.google.com/g/django-announce (opens in a new tab)
- github.com/django/django/commit/83cbd21be57483e6b3eb6e4688a561c841aff75e (opens in a new tab)
- github.com/django/django/commit/cce6c57ed30ea83725f9d6abb2fe5ee932bab107 (opens in a new tab)
- github.com/django/django/commit/b83ab92bc5474558b083a840ea4628b3261b2cfe (opens in a new tab)
- github.com/django/django/commit/ff27883ca055aa9ab23015b50674a5b10dfe5a41 (opens in a new tab)
- djangoproject.com/weblog/2026/oct/06/security-releases/ (opens in a new tab)