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%CVSS: 8.8Exploit: None knownExposed: 0

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.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 18, 2026

Advisory Details (7)

Auto-updated Aug 4, 2026
Upstream fix merged — awaiting tagged release. 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(8)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatansible-automation-platform/bootc-automation-portal-rhel9:17889435312026-09-09redhat
redhatpython3.12-django-0:5.2.17-1.el9ap2026-08-24redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17872440792026-08-24redhat
redhatansible-automation-platform-27/lightspeed-rhel9:17872175312026-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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-django2:2.2.24-1 ... 3:6.1~rc1-1 (185 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-django3:3.2.19-1 ... 3:6.1~rc1-1 (108 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-django3:4.2.23-1 ... 3:6.1~rc1-1 (63 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-django3:4.2.23-1 ... 3:5.2~rc1-1 (45 versions)3:5.2.17-1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 36× in last 7d / 135× 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 201 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 42.0% of all scored CVEs.
What is the CVSS score of CVE-2026-15307?
CVE-2026-15307 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-15307?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15307, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs