CVE-2026-15307 Details
Description
An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the `django.contrib.gis.gdal.GDALRaster` constructor. Any value used in a spatial lookup against a `GeometryField` or `RasterField` reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query string by a staff user with view permission. A `dict`, or a `str` holding its JSON representation, is opened in write mode regardless of the constructor's `write=False` default, allowing a file with an attacker-chosen name and contents to be written through a file-backed GDAL driver. Any other `str` is treated as a datasource, allowing an outbound network request through a GDAL virtual filesystem handler. Writing a file to a location later imported by the application can result in remote code execution. 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 Bence Nagy, localhost-detect, and kimchunbok_ for reporting this issue.
A vulnerability exists in Django versions 5.2 prior to 5.2.17 and 6.0 prior to 6.0.8, specifically within GeoDjango's spatial lookup functionality. The issue arises because the right-hand-side value in spatial lookups is optimistically interpreted as a raster and passed to the GDALRaster constructor. This behavior can be exploited by sending untrusted input through a spatial-field filter in the Django admin, potentially leading to unauthorized file writes or network requests. Such actions could be exploited to execute arbitrary code if the written file is later imported by the application.
Users can upgrade to Django versions 5.2.17 or 6.0.8, both of which include the necessary patch. Instructions for updating Django can be found in the Django documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Aug 4, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://docs.djangoproject.com/en/dev/releases/security/ | Django Software Foundation | PatchVendor Advisory |
| https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e | Django Software Foundation | Patch |
| https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa | Django Software Foundation | Patch |
| https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6 | Django Software Foundation | Patch |
| https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520 | Django Software Foundation | Patch |
| https://groups.google.com/g/django-announce | Django Software Foundation | Mailing List |
| https://www.djangoproject.com/weblog/2026/aug/04/security-releases/ | Django Software Foundation | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-73 | External Control of File Name or Path | Django Software Foundation |
| CWE-918 | Server-Side Request Forgery (SSRF) | Django Software Foundation |
Affected Products
| Product | Versions |
|---|---|
| djangoproject django | < 5.2.17 >= 6.0, < 6.0.8 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 24, 2026 | CVE Translated | [email protected] |
| Oct 23, 2026 | CVE Translated | [email protected] |
| Aug 18, 2026 | Initial Analysis | [email protected] |
| Aug 5, 2026 | CVE Modified | CISA-ADP |
| Aug 4, 2026 | CVE Modified | CISA-ADP |
| Aug 4, 2026 | New CVE Received | Django Software Foundation |