CVE-2026-15307

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” 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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-52747 (ENISA EUVD) · GHSA-wvqv-fj8w-qmhm (GitHub Security Advisories) · PYSEC-2026-4035 (OSV.dev)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG 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
67th
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-11-16). 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, 2026
Patch available. Sources: github_commit.
Web page

Django security releases issued: 6.0.8 and 5.2.17 | Weblog | Django

https://www.djangoproject.com/weblog/2026/aug/04/security-releases/
GitHub commit

commit 115ffd0463a7 (django/django)

Fix landed in django/django commit 115ffd0463a7 — awaiting tagged release

https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e
GitHub commit

commit 208f80cb6828 (django/django)

Fix landed in django/django commit 208f80cb6828 — awaiting tagged release

https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa
GitHub commit

commit 39b3e2d0c743 (django/django)

Fix landed in django/django commit 39b3e2d0c743 — awaiting tagged release

https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6
GitHub commit

commit f1949c1f9758 (django/django)

Fix landed in django/django commit f1949c1f9758 — awaiting tagged release

https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520
Web page

Archive of security issues | Django documentation | Django

https://docs.djangoproject.com/en/dev/releases/security/

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython3.12-django-0:4.2.30-3.el9pc2026-11-05redhat
redhatpython-django-0:4.2.30-2.el9pc2026-11-05redhat
redhatpython-pyyaml-0:6.0.1-1.el9pc2026-11-05redhat
ubuntupython3-django (3:5.2.9-0ubuntu4.3) @ resolute2026-10-27ubuntu
redhatansible-automation-platform-tech-preview/metrics-service-rhel9:17896545582026-09-23redhat
redhatansible-automation-platform-25/controller-rhel8:17896070212026-09-23redhat
redhatansible-automation-platform-27/metrics-service-rhel9:17889170582026-09-14redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17889435312026-09-09redhat
redhatansible-automation-platform-27/lightspeed-rhel9:17872175312026-08-24redhat
redhatpython3.12-django-0:5.2.17-1.el9ap2026-08-24redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17872293852026-08-24redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17872440792026-08-24redhat
pipDjango @ 5.2.17 (fixes < 5.2.17)—ghsa
pipDjango @ 6.0.8 (fixes >= 6.0a1, < 6.0.8)—ghsa

These rows come from Red Hat, Ubuntu and GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
py3-django—
  • every version up to 5.2.17-r0: fixed in 5.2.17-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-django2:2.2.24-1 ... 3:6.1~rc1-1 (185 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:3.2.19-1 ... 3:6.1~rc1-1 (114 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:4.2.23-1 ... 3:6.1~rc1-1 (67 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:4.2.23-1 ... 3:5.2~rc1-1 (45 versions)
  • every version up to 3:5.2.17-1: fixed in 3:5.2.17-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
django1.0.1 ... 6.0rc1 (435 versions)
  • every version up to 5.2.17: fixed in 5.2.17
  • 6.0a1 up to 6.0.8: fixed in 6.0.8
—

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 8× in last 7d / 38× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 321 rows 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 221 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:39 UTCEPSS rescoreEPSS 1.1% · 67th percentile
  2. 2026-11-20 16:37 UTCEPSS rescoreEPSS 1.1% · 67th percentile
  3. 2026-11-19 23:56 UTCOSV refresh
  4. 2026-11-19 16:33 UTCEPSS rescoreEPSS 1.1% · 67th percentile
  5. 2026-11-18 16:34 UTCEPSS rescoreEPSS 1.1% · 67th percentile
  6. 2026-11-17 16:34 UTCEPSS rescoreEPSS 1.1% · 67th percentile
  7. 2026-11-17 09:30 UTCEchelonGraph re-scored
  8. 2026-11-17 09:30 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-11-16 16:49 UTCEPSS rescoreEPSS 1.1% · 67th percentile
  10. 2026-11-14 16:39 UTCEPSS rescoreEPSS 1.1% · 67th percentile
  11. 2026-11-13 16:51 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  12. 2026-11-12 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  13. 2026-11-11 16:38 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  14. 2026-11-10 16:42 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  15. 2026-11-10 03:40 UTCEchelonGraph re-scored
  16. 2026-11-10 03:40 UTCVendor advisory
  17. 2026-11-10 03:40 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-11-09 16:34 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  19. 2026-11-08 16:38 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  20. 2026-11-07 16:38 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  21. 2026-11-06 16:36 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  22. 2026-11-05 16:36 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  23. 2026-11-04 16:34 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  24. 2026-11-03 16:47 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  25. 2026-11-03 12:17 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-03 12:17 UTCVendor advisory
  2. 2026-11-03 12:17 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-11-02 16:44 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  4. 2026-11-01 16:34 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  9. 2026-10-27 20:52 UTCEchelonGraph re-scored
  10. 2026-10-27 20:52 UTCVendor advisory
  11. 2026-10-27 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  12. 2026-10-26 16:30 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  13. 2026-10-25 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  14. 2026-10-25 14:47 UTCEchelonGraph re-scored
  15. 2026-10-24 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  16. 2026-10-24 16:28 UTCVendor advisory
  17. 2026-10-23 21:28 UTCEchelonGraph re-scored
  18. 2026-10-23 21:28 UTCVendor advisory
  19. 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  20. 2026-10-22 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  21. 2026-10-21 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  22. 2026-10-20 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  23. 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  24. 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  25. 2026-10-18 05:01 UTCEchelonGraph re-scored
  26. 2026-10-17 18:14 UTCEchelonGraph re-scored
  27. 2026-10-17 18:14 UTCVendor advisory
  28. 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  29. 2026-10-16 16:40 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  30. 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  31. 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  32. 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  33. 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  34. 2026-10-12 16:32 UTCEchelonGraph re-scored
  35. 2026-10-11 20:10 UTCEchelonGraph re-scored
  36. 2026-10-11 17:22 UTCEchelonGraph re-scored
  37. 2026-10-11 14:55 UTCEchelonGraph re-scored
  38. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  39. 2026-10-10 19:59 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  40. 2026-10-09 20:06 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  41. 2026-10-08 17:11 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  42. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  43. 2026-10-06 23:42 UTCEchelonGraph re-scored
  44. 2026-10-06 23:42 UTCVendor advisory
  45. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  46. 2026-10-05 19:43 UTCEchelonGraph re-scored
  47. 2026-10-05 19:43 UTCVendor advisory
  48. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  49. 2026-10-04 23:40 UTCVendor advisory
  50. 2026-10-04 06:12 UTCEchelonGraph re-scored
  51. 2026-10-04 06:12 UTCVendor advisory
  52. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  53. 2026-10-03 01:58 UTCEchelonGraph re-scored
  54. 2026-10-03 01:58 UTCVendor advisory
  55. 2026-10-02 10:11 UTCEchelonGraph re-scored
  56. 2026-10-02 10:11 UTCVendor advisory
  57. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  58. 2026-10-01 15:15 UTCVendor advisory
  59. 2026-10-01 02:27 UTCEchelonGraph re-scored
  60. 2026-10-01 02:27 UTCVendor advisory
  61. 2026-09-30 15:02 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  62. 2026-09-29 15:20 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  63. 2026-09-29 06:27 UTCEchelonGraph re-scored
  64. 2026-09-29 06:27 UTCVendor advisory
  65. 2026-09-29 06:26 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
  66. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  67. 2026-09-28 06:54 UTCVendor advisory
  68. 2026-09-28 06:54 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
  69. 2026-09-27 18:03 UTCEchelonGraph re-scored
  70. 2026-09-27 18:03 UTCVendor advisory
  71. 2026-09-27 18:03 UTCGHSA enrichmentGHSA-wvqv-fj8w-qmhm · GitHub severity HIGH · GitHub CVSS 8.8
  72. 2026-09-27 13:47 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  73. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  74. 2026-09-25 04:41 UTCEchelonGraph re-scored
  75. 2026-09-25 04:41 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-15307?
CVE-2026-15307 is a high-severity vulnerability; its CVE record was published on August 4, 2026. 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…
When was CVE-2026-15307 made public?
CVE-2026-15307 was made public on August 4, 2026: that is the date its CVE record's CNA, Django Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on August 4, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-15307 actively exploited?
CVE-2026-15307 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15307?
CVE-2026-15307 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15307?
A fix for CVE-2026-15307 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15307 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15307

Explore →

Is Your Infrastructure Affected by CVE-2026-15307?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.