CVE-2026-15337
mediumpriority · track · 0EPSS 0.006 · 48 %ileDEEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 2.7–6.9
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (16)
Products and version ranges known to be affected.
- Red Hat Ansible Automation Platform 2.5all versionscert_bundDEcpe:/a:redhat:ansible_automation_platform:2.5
- Red Hat Ansible Automation Platform 2.6all versionscert_bundDEcpe:/a:redhat:ansible_automation_platform:2.6
- Red Hat Ansible Automation Platform 2.7all versionscert_bundDEcpe:/a:redhat:ansible_automation_platform:2.7
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-2649Django: Mehrere SchwachstellenDeutsch2026-08-04csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Django ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen oder einen Denial-of-Service-Zustand auszulösen.
- BIT-django-2026-15337Potential denial-of-service vulnerability in check_for_language()2026-08-19vendor · osvUS
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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (21)
External citations — patches, advisories, analysis.
- https://docs.djangoproject.com/en/dev/releases/security/cnnvd
- https://github.com/django/django/commit/224dbc832586ad5cfb0237c2ff30d14baeaddc6fcnnvd
- https://github.com/django/django/commit/27137e655e442e81095f1f8f77ff3870d9fdf169cnnvd
- https://github.com/django/django/commit/5b3523d29be25948e1dd90b3863a002f00fc865fcnnvd
- https://github.com/django/django/commit/c72a5dbb64d0777f3f471f1be94e8b2ca91e0959cnnvd
- https://groups.google.com/g/django-announcecnnvd
- https://www.djangoproject.com/weblog/2026/aug/04/security-releases/cnnvd
- https://docs.djangoproject.com/en/dev/releases/security/enisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan