CVE-2026-87975: Python django · 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
Affects python-djangoSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium.
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.
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu Pro 14.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=esm-infra-legacy/trustyOther threats | Affected
| Fixed in– |
Ubuntu Pro 16.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=esm-infra-legacy/xenialOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=esm-infra/bionicOther threats | Affected
| Fixed in– |
Ubuntu Pro 20.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=esm-infra/focalOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=nobleOther 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
Fixed versions are available: Django 6.1.2, 6.0.9, and 5.2.18 address this vulnerability. Users should upgrade to these or later versions to remediate the issue. Since this is a software vulnerability with official fixes, applying the official patches is the recommended mitigation.
Description
A vulnerability in Django versions 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18 allows an authenticated user with permission to submit a formset to delete database rows outside the formset's limiting queryset. This occurs because the save_existing_objects() method incorrectly trusts the presence of a primary key in submitted form data as proof that the object belongs to the queryset, enabling deletion of unauthorized objects when certain primary key types are used. Models with default AutoField primary keys are not affected.
References
- nvd.nist.gov/vuln/detail/CVE-2026-87975 (opens in a new tab)
- github.com/django/django/commit/83cbd21be57483e6b3eb6e4688a561c841aff75e (opens in a new tab)
- github.com/django/django/commit/b83ab92bc5474558b083a840ea4628b3261b2cfe (opens in a new tab)
- github.com/django/django/commit/cce6c57ed30ea83725f9d6abb2fe5ee932bab107 (opens in a new tab)
- github.com/django/django/commit/ff27883ca055aa9ab23015b50674a5b10dfe5a41 (opens in a new tab)
- docs.djangoproject.com/en/dev/releases/security (opens in a new tab)
- groups.google.com/g/django-announce (opens in a new tab)
- djangoproject.com/weblog/2026/oct/06/security-releases (opens in a new tab)
- ubuntu.com/security/CVE-2026-87975 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-87975 (opens in a new tab)
- djangoproject.com/weblog/2026/oct/06/security-releases/ (opens in a new tab)