CVE-2026-15337
Potential denial-of-service vulnerability in check_for_language()
- Published
- Updated
- Reserved
- Assigned by
- DSF
Description
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| DSFCNA (assigner) | 4.0 | Medium6.9 | 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 |
| DSFCNA (assigner) | 3.1 | Medium5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| NVDNVD · Analyzed | 4.0 | Medium6.9 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
- EPSS (exploitation in 30 days)
- 0.59% · top 52% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.9.
Weakness
Affected products
- affected 6.0 – < 6.0.8
- unaffected 6.0.8
- affected 5.2 – < 5.2.17
- unaffected 5.2.17
References (7)
- Django security archive (opens in a new tab)vendor-advisory
- Django releases announcements (opens in a new tab)mailing-list
- https://github.com/django/django/commit/27137e655e442e81095f1f8f77ff3870d9fdf169 (opens in a new tab)patch
- https://github.com/django/django/commit/5b3523d29be25948e1dd90b3863a002f00fc865f (opens in a new tab)patch
- https://github.com/django/django/commit/224dbc832586ad5cfb0237c2ff30d14baeaddc6f (opens in a new tab)patch
- https://github.com/django/django/commit/c72a5dbb64d0777f3f471f1be94e8b2ca91e0959 (opens in a new tab)patch
- Django security releases issued: 6.0.8 and 5.2.17 (opens in a new tab)vendor-advisory
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2026-15337)Record last updated .