CVE-2026-87890: 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
Mentioned vulnerabilities
Not known to be exploited · CVSS 5.3 Medium : upgrade to 6.1.2 when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.1.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 to 6.1.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIdjangopkg:pypi/djangoOther threats | 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– |
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. There is no indication that earlier unsupported versions have official patches. No vendor advisory content contradicts this; therefore, upgrading is the recommended mitigation.
Description
A vulnerability in Django versions prior to 6.1.2, 6.0.9, and 5.2.18 allows an attacker who can supply bytes values to cause the Django process to make unintended network requests. This issue stems from an incomplete fix of a previous vulnerability related to spatial lookups involving crafted VRT documents referencing external raster sources. The vulnerability has a medium severity rating with a CVSS score of 5.3.
References
- nvd.nist.gov/vuln/detail/CVE-2026-87890 (opens in a new tab)
- github.com/django/django/commit/4e77ef1e69c94780006b82795aa7db101996c3af (opens in a new tab)
- github.com/django/django/commit/a2347fe8234a1831d56c875acc0ea51e0742957c (opens in a new tab)
- github.com/django/django/commit/dd0558d1617619e0d66163675ef02135d0f54e5f (opens in a new tab)
- github.com/django/django/commit/ebcb13b327301f28cbc6cd5e4988a719f00575aa (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-87890 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-87890 (opens in a new tab)
- djangoproject.com/weblog/2026/oct/06/security-releases/ (opens in a new tab)