djangoproject · Django · published 2026-08-04
CVE-2026-15307Server-side file-write and request forgery via spatial lookups
This month EPSS 1.1% with high severity (CVSS 8.7).
CVE-2026-15307 is not known to be exploited in the wild. EPSS estimates a 1.1% chance of exploitation in the next 30 days, higher than 67% of all CVEs. This Django vulnerability: CVSS 8.7 (v4.0), a successful attack gives total control of the component. Fixed upstream in Django 6.1.2, 6.0.9, 5.2.18; patched packages are out for Ubuntu; Debian still has unfixed releases. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Django 6.1.2, 6.0.9, 5.2.18.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | python-django | No fix yet |
| 12 bookworm | python-django | Won’t fix | |
| Ubuntu | 26.04 LTS | python-django | Fixed in 3:5.2.9-0ubuntu4.3 |
| 24.04 LTS | python-django | Fixed in 3:4.2.11-1ubuntu1.18 | |
| 22.04 LTS | python-django | Fixed in 2:3.2.12-2ubuntu1.29 |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Web frameworkDjango
Django security releases: 6.1.2, 6.0.9, 5.2.18
Upgrade to
6.1.26.0.95.2.18Why: CVE-2026-15307: EPSS 1.1% with high severity (CVSS 8.7).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 1.1% (67th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.7 (v4.0)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 | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- djangoproject Django
6.0to before6.0.8(affected)6.0.8(unaffected)5.2to before5.2.17(affected)5.2.17(unaffected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.