CVE-2026-87890
What it is
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. An incomplete fix for CVE-2026-15307 in Django spatial lookups allows an attacker who can supply `bytes` values to cause the Django process to make network requests via a crafted VRT document referencing an external raster source. 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 sicksec for reporting this issue.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 6.9 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-918 · Server-side request forgery
- Record status
- Deferred
Attack profile CVSS 4.0 · 6.9
- Attack vector
- Network
- Complexity
- Low
- Attack requirements
- None
- Privileges needed
- None
- User interaction
- None
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-87890.md and follow it. Check whether this project is affected by CVE-2026-87890. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/django/django/commit/4e77ef1e69c94780006b82795aa7db101996c3af
- https://github.com/django/django/commit/a2347fe8234a1831d56c875acc0ea51e0742957c
- https://github.com/django/django/commit/dd0558d1617619e0d66163675ef02135d0f54e5f
- https://github.com/django/django/commit/ebcb13b327301f28cbc6cd5e4988a719f00575aa
References
- https://docs.djangoproject.com/en/dev/releases/security/
- https://github.com/django/django/commit/4e77ef1e69c94780006b82795aa7db101996c3af
- https://github.com/django/django/commit/a2347fe8234a1831d56c875acc0ea51e0742957c
- https://github.com/django/django/commit/dd0558d1617619e0d66163675ef02135d0f54e5f
- https://github.com/django/django/commit/ebcb13b327301f28cbc6cd5e4988a719f00575aa
- https://groups.google.com/g/django-announce
- https://www.djangoproject.com/weblog/2026/oct/06/security-releases/