CVE-2026-15307

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • 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/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.1%
EPSS %ILE
64th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 4, 2026

Last Modified

August 18, 2026

Advisory Details (7)

Auto-updated Aug 4, 2026
Patch available. Sources: github_commit.
generic

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
generic
https://groups.google.com/g/django-announce
generic

Archive of security issues | Django documentation | Django

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

Vendor Advisories for CVE-2026-15307(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-django (1:1.11.11-1ubuntu1.21+esm17) @ bionic2026-10-04ubuntu
redhatansible-automation-platform-25/controller-rhel8:17896070212026-09-23redhat
redhatansible-automation-platform-tech-preview/metrics-service-rhel9:17896545582026-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-26/lightspeed-rhel9:17872440792026-08-24redhat
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

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)
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 (110 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 (64 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 18× in last 7d / 116× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 248 total refreshes for this CVE.

  1. 2026-10-04 23:40 UTCVendor advisory
  2. 2026-10-04 06:12 UTCEG score recompute
  3. 2026-10-04 06:12 UTCVendor advisory
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 01:58 UTCEG score recompute
  6. 2026-10-03 01:58 UTCVendor advisory
  7. 2026-10-02 10:11 UTCEG score recompute
  8. 2026-10-02 10:11 UTCVendor advisory
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-10-01 15:15 UTCVendor advisory
  11. 2026-10-01 02:27 UTCEG score recompute
  12. 2026-10-01 02:27 UTCVendor advisory
  13. 2026-09-30 15:02 UTCEPSS rescore
  14. 2026-09-29 15:20 UTCEPSS rescore
  15. 2026-09-29 06:27 UTCEG score recompute
  16. 2026-09-29 06:27 UTCVendor advisory
  17. 2026-09-29 06:26 UTCGHSA enrichment
  18. 2026-09-28 13:51 UTCEPSS rescore
  19. 2026-09-28 06:54 UTCVendor advisory
  20. 2026-09-28 06:54 UTCGHSA enrichment
  21. 2026-09-27 18:03 UTCEG score recompute
  22. 2026-09-27 18:03 UTCVendor advisory
  23. 2026-09-27 18:03 UTCGHSA enrichment
  24. 2026-09-27 13:47 UTCEPSS rescore
  25. 2026-09-26 15:58 UTCEPSS rescore
Show 75 more
  1. 2026-09-25 04:41 UTCEG score recompute
  2. 2026-09-25 04:41 UTCVendor advisory
  3. 2026-09-25 04:41 UTCGHSA enrichment
  4. 2026-09-24 12:49 UTCVendor advisory
  5. 2026-09-24 12:49 UTCGHSA enrichment
  6. 2026-09-23 23:46 UTCEG score recompute
  7. 2026-09-23 23:46 UTCVendor advisory
  8. 2026-09-23 23:46 UTCGHSA enrichment
  9. 2026-09-23 10:12 UTCVendor advisory
  10. 2026-09-23 10:12 UTCGHSA enrichment
  11. 2026-09-22 21:24 UTCEG score recompute
  12. 2026-09-22 21:24 UTCVendor advisory
  13. 2026-09-22 21:24 UTCGHSA enrichment
  14. 2026-09-22 03:23 UTCEG score recompute
  15. 2026-09-22 03:23 UTCVendor advisory
  16. 2026-09-22 03:23 UTCGHSA enrichment
  17. 2026-09-20 20:53 UTCEG score recompute
  18. 2026-09-20 20:53 UTCVendor advisory
  19. 2026-09-20 20:53 UTCGHSA enrichment
  20. 2026-09-19 23:23 UTCEG score recompute
  21. 2026-09-19 23:23 UTCVendor advisory
  22. 2026-09-19 23:23 UTCGHSA enrichment
  23. 2026-09-19 07:58 UTCEG score recompute
  24. 2026-09-19 07:58 UTCVendor advisory
  25. 2026-09-19 07:58 UTCGHSA enrichment
  26. 2026-09-18 19:27 UTCEPSS rescore
  27. 2026-09-18 17:50 UTCVendor advisory
  28. 2026-09-18 17:50 UTCGHSA enrichment
  29. 2026-09-18 05:02 UTCEG score recompute
  30. 2026-09-18 05:02 UTCVendor advisory
  31. 2026-09-18 05:02 UTCGHSA enrichment
  32. 2026-09-17 16:14 UTCVendor advisory
  33. 2026-09-17 16:14 UTCGHSA enrichment
  34. 2026-09-17 01:11 UTCEG score recompute
  35. 2026-09-17 01:11 UTCVendor advisory
  36. 2026-09-17 01:11 UTCGHSA enrichment
  37. 2026-09-16 14:07 UTCEPSS rescore
  38. 2026-09-16 05:36 UTCEG score recompute
  39. 2026-09-16 05:36 UTCVendor advisory
  40. 2026-09-16 05:35 UTCGHSA enrichment
  41. 2026-09-16 05:14 UTCEPSS rescore
  42. 2026-09-15 16:48 UTCEG score recompute
  43. 2026-09-15 16:48 UTCVendor advisory
  44. 2026-09-15 16:48 UTCGHSA enrichment
  45. 2026-09-15 01:40 UTCVendor advisory
  46. 2026-09-15 01:40 UTCGHSA enrichment
  47. 2026-09-14 06:53 UTCVendor advisory
  48. 2026-09-14 06:53 UTCGHSA enrichment
  49. 2026-09-13 18:06 UTCEG score recompute
  50. 2026-09-13 18:06 UTCVendor advisory
  51. 2026-09-13 18:06 UTCGHSA enrichment
  52. 2026-09-13 16:46 UTCEPSS rescore
  53. 2026-09-13 05:18 UTCVendor advisory
  54. 2026-09-13 05:18 UTCGHSA enrichment
  55. 2026-09-12 16:31 UTCEG score recompute
  56. 2026-09-12 16:31 UTCVendor advisory
  57. 2026-09-12 16:31 UTCGHSA enrichment
  58. 2026-09-12 15:00 UTCEPSS rescore
  59. 2026-09-12 03:40 UTCEG score recompute
  60. 2026-09-12 03:40 UTCVendor advisory
  61. 2026-09-12 03:40 UTCGHSA enrichment
  62. 2026-09-11 14:52 UTCEPSS rescore
  63. 2026-09-11 14:52 UTCEG score recompute
  64. 2026-09-11 14:52 UTCVendor advisory
  65. 2026-09-11 14:52 UTCGHSA enrichment
  66. 2026-09-11 09:36 UTCEPSS rescore
  67. 2026-09-10 21:04 UTCEG score recompute
  68. 2026-09-10 21:04 UTCVendor advisory
  69. 2026-09-10 21:04 UTCGHSA enrichment
  70. 2026-09-10 09:34 UTCEPSS rescore
  71. 2026-09-10 08:16 UTCVendor advisory
  72. 2026-09-10 08:16 UTCGHSA enrichment
  73. 2026-09-09 19:28 UTCVendor advisory
  74. 2026-09-09 19:28 UTCGHSA enrichment
  75. 2026-09-09 06:36 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-15307?
CVE-2026-15307 is a high vulnerability 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 disclosed?
CVE-2026-15307 was first published on August 4, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (64th 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.

Book a Demo →Browse All CVEs