CVE-2026-15307: Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
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.
Published Aug 4, 2026 · Updated Sep 30, 2026
Affected packages
Django
- Ecosystem
- PyPI
- Affected
- < 5.2.17
- Fixed in
- 5.2.17
- Check
pip show Django
Django
- Ecosystem
- PyPI
- Affected
- >= 6.0a1, < 6.0.8
- Fixed in
- 6.0.8
- Check
pip show Django
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to nazeeh111.
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-15307
- 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://docs.djangoproject.com/en/dev/releases/security
- https://groups.google.com/g/django-announce
- https://www.djangoproject.com/weblog/2026/aug/04/security-releases
- https://github.com/advisories/GHSA-wvqv-fj8w-qmhm
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-35192
Django Uses Persistent Cookies Containing Sensitive Information
low2.3May 5, 2026CVE-2026-5766
Django has an Improper Handling of Length Parameter Inconsistency
medium5.3May 5, 2026CVE-2026-6907
Django Uses Cache Containing Sensitive Information
low4.3May 5, 2026CVE-2026-33033
Django has potential DoS via MultiPartParser through crafted multipart uploads
medium6.5Apr 7, 2026CVE-2026-33034
Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit
high7.5Apr 7, 2026CVE-2026-3902
Django vulnerable to ASGI header spoofing via underscore/hyphen conflation
high7.5Apr 7, 2026
