CVE-2026-87890

Published: Ott 06, 2026 Last Modified: Ott 06, 2026
ExploitDB:
Other exploit source:
Google Dorks:
MEDIUM 6,9
Source: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A
MEDIUM 5,3
Source: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Scope: unchanged
Confidentiality: low
Integrity: none
Availability: none

Description

AI Translation Available

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.

918

Server-Side Request Forgery (SSRF)

Incomplete
Common Consequences
Security Scopes Affected:
Confidentiality Integrity Access Control
Potential Impacts:
Read Application Data Execute Unauthorized Code Or Commands Bypass Protection Mechanism
Applicable Platforms
Technologies: Web Based, AI/ML, Web Server
View CWE Details
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/