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
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| djangoproject | Django | 6.0 – < 6.0.8, 5.2 – < 5.2.17 | 6.0.8 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | python-django | 3:5.2.17-1 | — |
| Debian 13 | python-django | No fix yet | — |
| Debian 12 | python-django | 3:3.2.25-0+deb12u4 | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | python-django | No fix yet | — |
| Ubuntu 26.04 LTS | python-django | No fix yet | — |
| Ubuntu 24.04 LTS | python-django | No fix yet | — |
| Ubuntu 22.04 LTS | python-django | No fix yet | — |
Show 4 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu Pro 20.04 LTS | python-django | No fix yet | — |
| Ubuntu Pro 18.04 LTS | python-django | No fix yet | — |
| Ubuntu Pro 16.04 LTS | python-django | No fix yet | — |
| Ubuntu Pro 14.04 LTS | python-django | No fix yet | — |
SUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES 15 SP7 | python-Django | 4.2.11-150600.3.65.1 | SUSE-SU-2026:3503-1 |
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Tumbleweed | python-Django | 6.0.8-1.1 | openSUSE-SU-2026:11464-1 |
| openSUSE Tumbleweed | python-Django4 | 4.2.30-5.1 | openSUSE-SU-2026:11465-1 |
| openSUSE Tumbleweed | python-Django5 | 5.2.17-1.1 | openSUSE-SU-2026:11491-1 |
| openSUSE Leap 16.0 | python-Django | 5.2.4-bp160.11.1 | openSUSE-SU-2026:21543-1 |
Alpine
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Alpine v3.24 | py3-django | 5.2.17-r0 | — |
Advisories 6
- WID-SEC-2026-2649 Django: Mehrere Schwachstellen BSI CERT-Bund (WID) · Nov 5, 2026
- openSUSE-SU-2026:11491-1 python313-Django5-5.2.17-1.1 on GA media SUSE / openSUSE Security Updates · Aug 11, 2026
- openSUSE-SU-2026:21543-1 Security update for python-Django SUSE / openSUSE Security Updates · Aug 7, 2026
- openSUSE-SU-2026:11465-1 python313-Django4-4.2.30-5.1 on GA media SUSE / openSUSE Security Updates · Aug 7, 2026
- openSUSE-SU-2026:11464-1 python313-Django-6.0.8-1.1 on GA media SUSE / openSUSE Security Updates · Aug 7, 2026
- SUSE-SU-2026:3503-1 Security update for python-Django SUSE / openSUSE Security Updates · Aug 6, 2026
References
- Django security archive vendor-advisory
- Django releases announcements mailing-list
- https://github.com/django/django/commit/27137e655e442e81095f1f8f77ff3870d9fdf169 patch
- https://github.com/django/django/commit/5b3523d29be25948e1dd90b3863a002f00fc865f patch
- https://github.com/django/django/commit/224dbc832586ad5cfb0237c2ff30d14baeaddc6f patch
- https://github.com/django/django/commit/c72a5dbb64d0777f3f471f1be94e8b2ca91e0959 patch
- Django security releases issued: 6.0.8 and 5.2.17 vendor-advisory