CVE-2026-77050: medium-severity vulnerability in djangoproject Django
Potential denial-of-service vulnerability in get_supported_language_variant()
Published
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.9epss 0.4%
exploitation probability
0.4%top 70% of all CVEs
observed exploitation
nono source reports it
An issue was discovered in Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18.
`django.utils.translation.get_supported_language_variant()` is subject to
a potential denial-of-service attack when processing many distinct, very long
language codes, which are retained as keys in an in-memory cache and
consume process memory.
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 Gleb Lizunov for reporting this issue.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Affected products
djangoproject · DjangoRelated CVEs — djangoproject Django
In the same product, most dangerous first.
CVE-2025-64459CRITICALPotential SQL injection via _connector keyword argument in QuerySet and Q objectsEPSS 19.3%CVE-2025-57833HIGHCVE-2025-57833EPSS 16.8%CVE-2025-32873MEDIUMCVE-2025-32873EPSS 14.2%CVE-2026-1207MEDIUMPotential SQL injection via raster lookups on PostGISEPSS 12.8%CVE-2025-64460HIGHPotential denial-of-service vulnerability in XML serializer text extractionEPSS 2.1%CVE-2024-56374MEDIUMCVE-2024-56374EPSS 1.9%
References
https://docs.djangoproject.com/en/dev/releases/security/https://github.com/django/django/commit/02a69e3791e3df23d45ea4ea7e7fc489f0eef2behttps://github.com/django/django/commit/3d32ee80ae52745d686bf94d3555000ddf073267https://github.com/django/django/commit/7e878b0f8bd42260903e6a0d38996a93b0474a0bhttps://github.com/django/django/commit/c88b304cc2d90fc37d3bd1f5f3829706fa6c13bchttps://groups.google.com/g/django-announcehttps://www.djangoproject.com/weblog/2026/oct/06/security-releases/