CVE-2026-15337

published 4 Aug 2026 · updated 4 Aug 2026

Potential denial-of-service vulnerability in check_for_language()

5.3MediumCVSS 5.3EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 5.2.17 and 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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
djangoproject>=5.2 <5.2.17, >=6.0 <6.0.85.2.17, 6.0.8

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-15337 severity on Zeptric[![CVE-2026-15337](https://zeptric.io/badge/cve/CVE-2026-15337.svg)](https://zeptric.io/cve/CVE-2026-15337)