python-django: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8
CVE-2026-15337 is fixed in 2 products on 1 platform, first by SUSE-SU-2026:3503-1, released August 5, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| python-Django · opensuse-leap 16.0 | 5.2.4-bp160.11.1 | OPENSUSE-SU-2026:21543-1 | Aug 6, 2026 |
| python-Django · sles 15.7 | 4.2.11-150600.3.65.1 | SUSE-SU-2026:3503-1 | Aug 5, 2026 |
| python-django · Debian 12.15 (bookworm) | 3:3.2.25-0+deb12u4 | DEBIAN-CVE-2026-15337 | Aug 13, 2026 |
| python-django · Debian 14 | 3:5.2.17-1 | DEBIAN-CVE-2026-15337 | Aug 13, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.