CVE-2026-15307 — Server-side file-write and request forgery via spatial lookups
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — docs.djangoproject.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Djangoproject Django).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Djangoproject | Django | < 5.2.17≥ 6.0 and < 6.0.8 | Vulnerable | NIST National Vulnerability Database |
| Djangoproject | Django | ≥ 6.0 and < 6.0.8≥ 5.2 and < 5.2.17 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.7 | CVSS 4.0 | High | — | — | 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 via NIST National Vulnerability Database |
| 8.7 | CVSS 4.0 | High | — | — | DSF via CVE Program (cve.org) e CISA ADP |
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | DSF via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · djangoproject/django
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 8.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
7 on the record
- www.djangoproject.com/weblog/2026/aug/04/security-releases/
- github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6
- github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520
- docs.djangoproject.com/en/dev/releases/security/
- github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa
- github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e
- groups.google.com/g/django-announce
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-87975 Privilege abuse in model formsets with editable primary keys 9d
- Medium CVE-2026-87890 Potential request forgery via spatial lookup byte values 9d
- Medium CVE-2026-84429 Potential denial-of-service vulnerability in HTTP header parsing 9d
- Medium CVE-2026-77050 Potential denial-of-service vulnerability in get_supported_language_variant() 9d
- Medium CVE-2026-15337 Potential denial-of-service vulnerability in check_for_language() Aug 4, 2026
- Medium CVE-2026-15830 Potential denial-of-service vulnerability via nested geometry collections Aug 4, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-15307 is "Server-side file-write and request forgery via spatial lookups", rated High. It affects Django (Djangoproject); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.