Django 5.2/6.0 DOS via long lang codes (pre-5.2.17, pre-6.0.8)
CVE-2026-15337 Published on August 4, 2026
Potential denial-of-service vulnerability in check_for_language()
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.
Timeline
Initial report received.
Vulnerability confirmed. 19 days later.
Security release issued. 14 days later.
Weakness Type
What is a Stack Exhaustion Vulnerability?
The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.
CVE-2026-15337 has been classified to as a Stack Exhaustion vulnerability or weakness.
Products Associated with CVE-2026-15337
Want to know whenever a new CVE is published for Django Project Django? stack.watch will email you.
Affected Versions
djangoproject Django:- Version 6.0 and below 6.0.8 is affected.
- Version 6.0.8 is unaffected.
- Version 5.2 and below 5.2.17 is affected.
- Version 5.2.17 is unaffected.