CVE Watchtower

CVE-2026-15337djangoproject Django

NVD

Vulnerability Summary

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.
Severity Level
MEDIUM(5.3)
Published Date
Aug 4, 2026
Last Modified
Aug 4, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
1.03%Probability
Root Weakness (CWE)
See the MITRE CWE entry for the full definition of this weakness.
CVSS v4.0 Base Metrics — Score 6.9 (MEDIUM)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsNone
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)None
Integrity (Vulnerable System)None
Availability (Vulnerable System)Low
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Show CVSS v3.x metrics (score 5.3)
CVSS v3.1 Base Metrics — Score 5.3 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityLow

Affected & Patched Versions

Affected Versions
  • djangoproject Django >= 6.0 and < 6.0.8
  • djangoproject Django >= 5.2 and < 5.2.17
Patched Versions
  • djangoproject Django 6.0.8
  • djangoproject Django 5.2.17

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run djangoproject Django and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Aug 4, 2026Published
  • Aug 4, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new djangoproject Django CVEsYou are reading CVE-2026-15337. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 18, 2026 18:39 UTC