CVE-2026-15830

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM 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: 0.8%CVSS: 5.3Exploit: 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'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.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/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
Severity53% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 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

(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.0.7 (432 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
  • 6.1a1 up to 6.1.1: fixed in 6.1.1
  • 6.0 up to 6.0.8: fixed in 6.0.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 59× 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 150 total refreshes for this CVE.

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

Related CVEs(same product + 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 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 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15830?
CVE-2026-15830 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15830?
A fix for CVE-2026-15830 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15830 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-15830

Explore →

Is Your Infrastructure Affected by CVE-2026-15830?

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

Book a Demo →Browse All CVEs