CVE-2026-15307
8.8 HIGHpublic exploit availablePublished 2026-08-04 · Updated 2026-08-05
AI risk analysis
- Summary
- The flaw allows untrusted input to be interpreted as a raster, potentially leading to file writing or network requests, which could result in remote code execution.
- Exploitability
- Exploitation requires a staff user with view permission and the ability to submit a spatial-field filter through the Django admin changelist query string. The attack surface is limited to authenticated users with specific permissions.
- Blast radius
- If exploited, the impact could be severe, as it allows for remote code execution, potentially leading to full compromise of the application and underlying systems.
- Detection
- No reliable host or network indicator is derivable from the published description.
- Prioritized remediation
- Upgrade to Django 5.2.17 or 6.0.8 or later.
Analysis generated locally by qwen2.5:7b-instruct (no data left the box). AI-assisted — verify against primary sources before acting.
NVD 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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-73, CWE-918
Public exploit & PoC references
- https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e
- https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa
- https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6
- https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520
All references
- https://docs.djangoproject.com/en/dev/releases/security/
- https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e
- https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa
- https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6
- https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520
- https://groups.google.com/g/django-announce
- https://www.djangoproject.com/weblog/2026/aug/04/security-releases/
Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.
Related CVEs
- HIGHCVE-2026-18813PoC
- HIGHCVE-2026-18898PoC
- HIGHCVE-2026-71239PoC
- CRITICALCVE-2026-74849
- CRITICALCVE-2026-88404PoC
- CRITICALCVE-2026-88405PoC
- HIGHCVE-2026-51997PoC
- HIGHCVE-2026-60009PoC
Related by shared AI tags and CWE weakness class. Browse the full archive.