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.
CVE-2026-15307
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-04. A secondary CVSS source baseline 8.8; sources differ by 0.0.
Also known asEUVD-2026-52747 (ENISA EUVD) · GHSA-wvqv-fj8w-qmhm (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation1.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 1.1%
- EPSS %ILE
- 66th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
August 4, 2026
Last Modified
October 24, 2026
Advisory Details (7)
Auto-updated Aug 4, 2026Django security releases issued: 6.0.8 and 5.2.17 | Weblog | Django
https://www.djangoproject.com/weblog/2026/aug/04/security-releases/commit 115ffd0463a7 (django/django)
Fix landed in django/django commit 115ffd0463a7 — awaiting tagged release
https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300ecommit 208f80cb6828 (django/django)
Fix landed in django/django commit 208f80cb6828 — awaiting tagged release
https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aacommit 39b3e2d0c743 (django/django)
Fix landed in django/django commit 39b3e2d0c743 — awaiting tagged release
https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6commit f1949c1f9758 (django/django)
Fix landed in django/django commit f1949c1f9758 — awaiting tagged release
https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520Archive of security issues | Django documentation | Django
https://docs.djangoproject.com/en/dev/releases/security/Vendor Advisories for CVE-2026-15307(12)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:92861Red Hat Product SecurityCritical
Red Hat Security Advisory: Satellite 6.19 security update
- RHSA-2026:71210Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Container Release Update
- RHSA-2026:71179Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.6 Container Release Update
- RHSA-2026:67279Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.7 Container Release Update
- RHSA-2026:66003Red Hat Product SecurityHigh
Red Hat Security Advisory: Ansible automation portal Red Hat Enterprise Linux Images
- RHSA-2026:59159Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Container Release Update
- RHSA-2026:59155Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.6 Container Release Update
- RHSA-2026:59153Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.7 Container Release Update
- +4 more
Patch Availability(9)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | python3-django (3:5.2.9-0ubuntu4.3) @ resolute | 2026-10-27 | ubuntu |
| redhat | ansible-automation-platform-25/controller-rhel8:1789607021 | 2026-09-23 | redhat |
| redhat | ansible-automation-platform-tech-preview/metrics-service-rhel9:1789654558 | 2026-09-23 | redhat |
| redhat | ansible-automation-platform-27/metrics-service-rhel9:1788917058 | 2026-09-14 | redhat |
| redhat | ansible-automation-platform/bootc-automation-portal-rhel9:1788943531 | 2026-09-09 | redhat |
| redhat | ansible-automation-platform-25/lightspeed-rhel8:1787229385 | 2026-08-24 | redhat |
| redhat | python3.12-django-0:5.2.17-1.el9ap | 2026-08-24 | redhat |
| redhat | ansible-automation-platform-26/lightspeed-rhel9:1787244079 | 2026-08-24 | redhat |
| redhat | ansible-automation-platform-27/lightspeed-rhel9:1787217531 | 2026-08-24 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-django | 2:2.2.24-1 ... 3:6.1~rc1-1 (185 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-django | 3:3.2.19-1 ... 3:6.1~rc1-1 (110 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-django | 3:4.2.23-1 ... 3:6.1~rc1-1 (64 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-django | 3:4.2.23-1 ... 3:5.2~rc1-1 (45 versions) |
| — |
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| django | 1.0.1 ... 6.0rc1 (435 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 9× in last 7d / 49× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 293 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 193 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-27 20:52 UTCEG score recompute
- 2026-10-27 20:52 UTCVendor advisory
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-25 14:47 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-24 16:28 UTCVendor advisory
- 2026-10-23 21:28 UTCEG score recompute
- 2026-10-23 21:28 UTCVendor advisory
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-18 05:01 UTCEG score recompute
- 2026-10-17 18:14 UTCEG score recompute
- 2026-10-17 18:14 UTCVendor advisory
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
Show 75 moreShow fewer
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-12 16:32 UTCEG score recompute
- 2026-10-11 20:10 UTCEG score recompute
- 2026-10-11 17:22 UTCEG score recompute
- 2026-10-11 14:55 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-08 17:11 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.1% · 65th percentile
- 2026-10-06 23:42 UTCEG score recompute
- 2026-10-06 23:42 UTCVendor advisory
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-05 19:43 UTCEG score recompute
- 2026-10-05 19:43 UTCVendor advisory
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-04 23:40 UTCVendor advisory
- 2026-10-04 06:12 UTCEG score recompute
- 2026-10-04 06:12 UTCVendor advisory
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-03 01:58 UTCEG score recompute
- 2026-10-03 01:58 UTCVendor advisory
- 2026-10-02 10:11 UTCEG score recompute
- 2026-10-02 10:11 UTCVendor advisory
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-01 15:15 UTCVendor advisory
- 2026-10-01 02:27 UTCEG score recompute
- 2026-10-01 02:27 UTCVendor advisory
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-09-29 15:20 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-09-29 06:27 UTCEG score recompute
- 2026-09-29 06:27 UTCVendor advisory
- 2026-09-29 06:26 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-09-28 06:54 UTCVendor advisory
- 2026-09-28 06:54 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-27 18:03 UTCEG score recompute
- 2026-09-27 18:03 UTCVendor advisory
- 2026-09-27 18:03 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-27 13:47 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-09-25 04:41 UTCEG score recompute
- 2026-09-25 04:41 UTCVendor advisory
- 2026-09-25 04:41 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-24 12:49 UTCVendor advisory
- 2026-09-24 12:49 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-23 23:46 UTCEG score recompute
- 2026-09-23 23:46 UTCVendor advisory
- 2026-09-23 23:46 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-23 10:12 UTCVendor advisory
- 2026-09-23 10:12 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-22 21:24 UTCEG score recompute
- 2026-09-22 21:24 UTCVendor advisory
- 2026-09-22 21:24 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-22 03:23 UTCEG score recompute
- 2026-09-22 03:23 UTCVendor advisory
- 2026-09-22 03:23 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-20 20:53 UTCEG score recompute
- 2026-09-20 20:53 UTCVendor advisory
- 2026-09-20 20:53 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-19 23:23 UTCEG score recompute
- 2026-09-19 23:23 UTCVendor advisory
- 2026-09-19 23:23 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-19 07:58 UTCEG score recompute
- 2026-09-19 07:58 UTCVendor advisory
- 2026-09-19 07:58 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.9% · 57th percentile
- 2026-09-18 17:50 UTCVendor advisory
- 2026-09-18 17:50 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-09-18 05:02 UTCEG score recompute
- 2026-09-18 05:02 UTCVendor advisory
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:11:python-django
- CVE-2026-4277EG 9.8CRITICAL
- CVE-2025-59681EG 9.8CRITICAL
- CVE-2023-31047EG 9.8CRITICAL
- CVE-2022-34265EG 9.8EPSS p99CRITICAL
- CVE-2022-28347EG 9.8CRITICAL
- CVE-2022-28346EG 9.8EPSS p97CRITICAL
- CVE-2020-7471EG 9.8EPSS p99CRITICAL
- CVE-2019-19844EG 9.8EPSS p99CRITICAL
- CVE-2019-14234EG 9.8EPSS p99CRITICAL
- CVE-2016-9013EG 9.8EPSS p92CRITICAL
Same vendor
10 shownredhat:RHSA-2026:59135 · redhat:RHSA-2026:59155
Frequently asked(5)
What is CVE-2026-15307?
When was CVE-2026-15307 made public?
Is CVE-2026-15307 actively exploited?
What is the CVSS score of CVE-2026-15307?
How do I remediate CVE-2026-15307?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15307
Is Your Infrastructure Affected by CVE-2026-15307?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.