CVE-2026-15307 Server-side file-write and request forgery via spatial lookups
Attackers can trigger server-side file writes and network requests via spatial lookups, potentially leading to remote code execution.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-15307?
CVE-2026-15307 is a high-severity server-side request forgery vulnerability in Djangoproject Django, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2026-15307?
6 open source packages ship an affected version, including django and Django. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django Bitnami | All versions | 5.2.17, 6.0.8 |
django PyPI | All versions | 5.2.17, 6.0.8 |
django PyPI | All versions | 5.2.17 |
django PyPI | From 6.0a1 | 6.0.8 |
Django PyPI | All versions | 5.2.17 |
Django PyPI | From 6.0a1 | 6.0.8 |
Products include Djangoproject Django.
How do I fix CVE-2026-15307?
Upgrade django to a fixed version for your release line: 5.2.17 or 6.0.8.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-15307 being exploited?
There is no known exploitation of CVE-2026-15307 in the wild and no public exploit code.
Other vulnerabilities in Djangoproject Django
- CVE-2026-4277 Privilege abuse in GenericInlineModelAdmin
- CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle
- CVE-2024-42005 Django SQL injection vulnerability
- CVE-2023-31047 Django bypasses validation when using one form field to upload multiple files
- CVE-2022-34265 Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection
Sources
Also known as BIT-django-2026-15307, DEBIAN-CVE-2026-15307, ECHO-fda4-bdd4-43f5, GHSA-wvqv-fj8w-qmhm, MINI-26j7-vx32-vh87, MINI-f6wc-7wwf-4cqv and 3 more.