CVE-2026-15337 — An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8…
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — docs.djangoproject.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Djangoproject Django).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Djangoproject | Django | < 5.2.17≥ 6.0 and < 6.0.8 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.9 | CVSS 4.0 | Medium | — | — | 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 via NIST National Vulnerability Database |
| 5.3 | CVSS 3.1 | Medium | 3.9 | 1.4 | 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L (score shown at the top: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Fix documented
- CVSS changed · 5.3
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
7 on the record
- www.djangoproject.com/weblog/2026/aug/04/security-releases/
- github.com/django/django/commit/27137e655e442e81095f1f8f77ff3870d9fdf169
- docs.djangoproject.com/en/dev/releases/security/
- github.com/django/django/commit/5b3523d29be25948e1dd90b3863a002f00fc865f
- github.com/django/django/commit/224dbc832586ad5cfb0237c2ff30d14baeaddc6f
- github.com/django/django/commit/c72a5dbb64d0777f3f471f1be94e8b2ca91e0959
- groups.google.com/g/django-announce
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-87975 Privilege abuse in model formsets with editable primary keys 9d
- Medium CVE-2026-87890 Potential request forgery via spatial lookup byte values 9d
- Medium CVE-2026-84429 Potential denial-of-service vulnerability in HTTP header parsing 9d
- Medium CVE-2026-77050 Potential denial-of-service vulnerability in get_supported_language_variant() 9d
- High CVE-2026-15307 An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango… Aug 4, 2026
- Medium CVE-2026-15830 Potential denial-of-service vulnerability via nested geometry collections Aug 4, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-15337 is "An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8…", rated Medium. It affects Django (Djangoproject); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.