Skip to content
fr Sign in
5.3 Medium

CVE-2026-15337 An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8

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.

Affected products and versions

Product Affected versions Fixed in
Django 6.0 6.0 → < 6.0.8 6.0.8
Django 5.2 5.2 → < 5.2.17 5.2.17

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Django

The 62 CVEs of Django →
CVE-2026-114582 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 5.3 Medium CVE-2026-113733 An issue was discovered in Django 6.1 before 6.1.3 and 6.0 before 6.0.10 2.2 Low CVE-2026-113593 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 3.1 Low CVE-2026-111362 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 5.3 Medium
Track this CVE