CVE-2026-15307
Server-side file-write and request forgery via spatial lookups
- Published
- Updated
- Reserved
- Assigned by
- DSF
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| DSFCNA (assigner) | 4.0 | High8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| DSFCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 4.0 | High8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
- EPSS (exploitation in 30 days)
- 1.1% · top 33% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.7.
Weakness
Affected products
- affected 6.0 – < 6.0.8
- unaffected 6.0.8
- affected 5.2 – < 5.2.17
- unaffected 5.2.17
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- PyPIDjangoGHSA-wvqv-fj8w-qmhm (opens in a new tab)
References (7)
- Django security archive (opens in a new tab)vendor-advisory
- Django releases announcements (opens in a new tab)mailing-list
- https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520 (opens in a new tab)patch
- https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6 (opens in a new tab)patch
- https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa (opens in a new tab)patch
- https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e (opens in a new tab)patch
- Django security releases issued: 6.0.8 and 5.2.17 (opens in a new tab)vendor-advisory
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-wvqv-fj8w-qmhm (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2026-15307)Record last updated .