CVE-2026-15337
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 0.6% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.6% in the next 30 days (EPSS).
- Severity: 6.9 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.6% · EPSS, next 30 days
- Weakness
- CWE-789
- Record status
- Analyzed
Affected
- Djangoproject Django < 5.2.17
- Djangoproject Django < 6.0.8
Attack profile CVSS 4.0 · 6.9
- Attack vector
- Network
- Complexity
- Low
- Attack requirements
- None
- Privileges needed
- None
- User interaction
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
Raw vector
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
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-15337.md and follow it. Check whether this project is affected by CVE-2026-15337. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://docs.djangoproject.com/en/dev/releases/security/
- https://github.com/django/django/commit/224dbc832586ad5cfb0237c2ff30d14baeaddc6f
- https://github.com/django/django/commit/27137e655e442e81095f1f8f77ff3870d9fdf169
- https://github.com/django/django/commit/5b3523d29be25948e1dd90b3863a002f00fc865f
- https://github.com/django/django/commit/c72a5dbb64d0777f3f471f1be94e8b2ca91e0959
- https://www.djangoproject.com/weblog/2026/aug/04/security-releases/
References
- https://docs.djangoproject.com/en/dev/releases/security/
- https://github.com/django/django/commit/224dbc832586ad5cfb0237c2ff30d14baeaddc6f
- https://github.com/django/django/commit/27137e655e442e81095f1f8f77ff3870d9fdf169
- https://github.com/django/django/commit/5b3523d29be25948e1dd90b3863a002f00fc865f
- https://github.com/django/django/commit/c72a5dbb64d0777f3f471f1be94e8b2ca91e0959
- https://groups.google.com/g/django-announce
- https://www.djangoproject.com/weblog/2026/aug/04/security-releases/