CVE-2026-15337

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. django.utils.translation.check_for_language() is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the django.views.i18n.set_language() view, which is not routed by default. The consumed memory is bounded, since request data is limited by the DATA_UPLOAD_MAX_MEMORY_SIZE setting (default 2.5 MB) and the cache holds a fixed maximum number of entries. 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 Jaeyoung Jang for reporting this issue.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
24(Track)
EG Risk 24/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%
Automatability0% × 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 c72a5dbb64d0 (django/django)

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

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

commit 224dbc832586 (django/django)

Fix landed in django/django commit 224dbc832586 — awaiting tagged release

https://github.com/django/django/commit/224dbc832586ad5cfb0237c2ff30d14baeaddc6f
github_commit

commit 5b3523d29be2 (django/django)

Fix landed in django/django commit 5b3523d29be2 — awaiting tagged release

https://github.com/django/django/commit/5b3523d29be25948e1dd90b3863a002f00fc865f
github_commit

commit 27137e655e44 (django/django)

Fix landed in django/django commit 27137e655e44 — awaiting tagged release

https://github.com/django/django/commit/27137e655e442e81095f1f8f77ff3870d9fdf169
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-15337(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 19× in last 7d / 49× 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 19:56 UTCGHSA enrichment
  3. 2026-08-19 18:56 UTCEG score recompute
  4. 2026-08-19 18:56 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  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 01:54 UTCEG score recompute
  10. 2026-08-18 01:54 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 00:56 UTCEG score recompute
  13. 2026-08-17 00:56 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 23:59 UTCEG score recompute
  17. 2026-08-15 23:59 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 23:01 UTCGHSA enrichment
  20. 2026-08-13 22:04 UTCEG score recompute
  21. 2026-08-13 22:04 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 21:08 UTCEG score recompute
  24. 2026-08-12 21:08 UTCGHSA enrichment
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 24 more
  1. 2026-08-12 01:03 UTCEG score recompute
  2. 2026-08-12 01:03 UTCGHSA enrichment
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-11 00:06 UTCEG score recompute
  5. 2026-08-11 00:06 UTCGHSA enrichment
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-09 23:09 UTCEG score recompute
  8. 2026-08-09 23:09 UTCGHSA enrichment
  9. 2026-08-09 13:46 UTCEPSS rescore
  10. 2026-08-08 22:13 UTCEG score recompute
  11. 2026-08-08 22:13 UTCGHSA enrichment
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-07 21:16 UTCEG score recompute
  14. 2026-08-07 21:16 UTCGHSA enrichment
  15. 2026-08-06 20:19 UTCEG score recompute
  16. 2026-08-06 20:19 UTCGHSA enrichment
  17. 2026-08-06 13:46 UTCEPSS rescore
  18. 2026-08-05 19:22 UTCEG score recompute
  19. 2026-08-05 19:22 UTCGHSA enrichment
  20. 2026-08-05 19:17 UTCEPSS rescore
  21. 2026-08-04 18:25 UTCEG score recompute
  22. 2026-08-04 17:23 UTCEG score recompute
  23. 2026-08-04 16:28 UTCEG score recompute
  24. 2026-08-04 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15337?
CVE-2026-15337 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. django.utils.translation.checkforlanguage() is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory.…
When was CVE-2026-15337 disclosed?
CVE-2026-15337 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-15337 actively exploited?
CVE-2026-15337 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-15337?
CVE-2026-15337 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-15337?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15337, 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-15337

Explore →

Is Your Infrastructure Affected by CVE-2026-15337?

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

Start Free Scan →Browse All CVEs