CVE-2026-87890: medium-severity vulnerability in djangoproject Django
Potential request forgery via spatial lookup byte values
Published
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.9epss 0.3%
exploitation probability
0.3%top 81% of all CVEs
observed exploitation
nono source reports it
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.
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
Affected products
djangoproject · DjangoRelated CVEs — djangoproject Django
In the same product, most dangerous first.
CVE-2025-64459CRITICALPotential SQL injection via _connector keyword argument in QuerySet and Q objectsEPSS 19.3%CVE-2025-57833HIGHCVE-2025-57833EPSS 16.8%CVE-2025-32873MEDIUMCVE-2025-32873EPSS 14.2%CVE-2026-1207MEDIUMPotential SQL injection via raster lookups on PostGISEPSS 12.8%CVE-2025-64460HIGHPotential denial-of-service vulnerability in XML serializer text extractionEPSS 2.1%CVE-2024-56374MEDIUMCVE-2024-56374EPSS 1.9%
References
https://docs.djangoproject.com/en/dev/releases/security/https://github.com/django/django/commit/4e77ef1e69c94780006b82795aa7db101996c3afhttps://github.com/django/django/commit/a2347fe8234a1831d56c875acc0ea51e0742957chttps://github.com/django/django/commit/dd0558d1617619e0d66163675ef02135d0f54e5fhttps://github.com/django/django/commit/ebcb13b327301f28cbc6cd5e4988a719f00575aahttps://groups.google.com/g/django-announcehttps://www.djangoproject.com/weblog/2026/oct/06/security-releases/