CVE-2026-15830

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-08-04. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's django.contrib.gis.geos.GEOSGeometry is subject to a potential denial-of-service when parsing deeply nested GEOMETRYCOLLECTION objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the django.contrib.gis.forms.GeometryField form field are also affected. 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 Andrew MacPherson and kimchunbok_ for reporting this issue.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/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
Severity53% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
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 ba80833fa656 (django/django)

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

https://github.com/django/django/commit/ba80833fa656dd09660b97c4429331067db1b080
github_commit

commit 6af5da317754 (django/django)

Fix landed in django/django commit 6af5da317754 — awaiting tagged release

https://github.com/django/django/commit/6af5da31775417c610dbf9c3f1b5b8333d42daf6
github_commit

commit 9e4a3f186b6b (django/django)

Fix landed in django/django commit 9e4a3f186b6b — awaiting tagged release

https://github.com/django/django/commit/9e4a3f186b6b07b483bfd9195ea06734663fcd06
github_commit

commit d2e59b77fe18 (django/django)

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

https://github.com/django/django/commit/d2e59b77fe18de318a8272c2a7bbc798d84d1d0d
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-15830(1)

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

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 (105 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-django3:4.2.23-1 ... 3:6.1~rc1-1 (61 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-django3:4.2.23-1 ... 3:6.1~rc1-1 (58 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 51× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 14:21 UTCEG score recompute
  3. 2026-08-20 14:21 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 15:21 UTCGHSA enrichment
  6. 2026-08-18 16:47 UTCEG score recompute
  7. 2026-08-18 16:46 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 11:51 UTCEG score recompute
  10. 2026-08-18 11:51 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 13:24 UTCGHSA enrichment
  13. 2026-08-16 14:57 UTCEG score recompute
  14. 2026-08-16 14:57 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 16:30 UTCEG score recompute
  18. 2026-08-15 16:30 UTCGHSA enrichment
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 18:02 UTCEG score recompute
  21. 2026-08-14 18:02 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 19:35 UTCGHSA enrichment
  24. 2026-08-12 21:08 UTCEG score recompute
  25. 2026-08-12 21:08 UTCGHSA enrichment
Show 26 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-12 06:07 UTCEG score recompute
  3. 2026-08-12 06:07 UTCGHSA enrichment
  4. 2026-08-11 13:42 UTCEPSS rescore
  5. 2026-08-11 07:38 UTCEG score recompute
  6. 2026-08-11 07:38 UTCGHSA enrichment
  7. 2026-08-11 00:00 UTCEPSS rescore
  8. 2026-08-10 09:11 UTCEG score recompute
  9. 2026-08-10 09:11 UTCGHSA enrichment
  10. 2026-08-09 13:46 UTCEPSS rescore
  11. 2026-08-09 10:44 UTCEG score recompute
  12. 2026-08-09 10:44 UTCGHSA enrichment
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-08 12:17 UTCEG score recompute
  15. 2026-08-08 12:17 UTCGHSA enrichment
  16. 2026-08-07 13:49 UTCGHSA enrichment
  17. 2026-08-06 15:22 UTCEG score recompute
  18. 2026-08-06 15:22 UTCGHSA enrichment
  19. 2026-08-06 13:46 UTCEPSS rescore
  20. 2026-08-05 19:17 UTCEPSS rescore
  21. 2026-08-05 16:54 UTCEG score recompute
  22. 2026-08-05 16:54 UTCGHSA enrichment
  23. 2026-08-04 18:25 UTCEG score recompute
  24. 2026-08-04 17:23 UTCEG score recompute
  25. 2026-08-04 16:28 UTCEG score recompute
  26. 2026-08-04 16:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15830?
CVE-2026-15830 is a medium 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's django.contrib.gis.geos.GEOSGeometry is subject to a potential denial-of-service when parsing deeply nested GEOMETRYCOLLECTION objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded…
When was CVE-2026-15830 disclosed?
CVE-2026-15830 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-15830 actively exploited?
CVE-2026-15830 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 57.8% of all scored CVEs.
What is the CVSS score of CVE-2026-15830?
CVE-2026-15830 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-15830?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15830, 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-15830

Explore →

Is Your Infrastructure Affected by CVE-2026-15830?

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

Start Free Scan →Browse All CVEs