# CVE-2026-77050: Django language code processing denial-of-service

Source: https://junglewise.ai/threats/cve-2026-77050-an-issue-was-discovered-in-django-6-1-before-6-1-2-6-0-before-6-0  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-06. Updated: 2026-10-06  
License: CC BY 4.0 with a link back

CVE-2026-77050 · Severity: medium · CVSS 5.3 · Published 2026-10-06

Django, a widely-used Python web framework, has a vulnerability in its language translation utilities where processing many long language codes causes unbounded memory consumption in a cache. An attacker can trigger a denial-of-service attack by submitting requests with distinct, lengthy language codes, exhausting server memory and causing the application to become unresponsive or crash.

Technologies: [Django Software Foundation Django](https://junglewise.ai/threats/technologies/django-software-foundation-django). Vendors: [Django Software Foundation](https://junglewise.ai/threats/vendors/django-software-foundation).

## Quick answers

**Is CVE-2026-77050 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-77050 being exploited in the wild.

**How severe is CVE-2026-77050?** Medium severity, with a CVSS score of 5.3, published 6 October 2026.

**Which products and versions are affected?** Django Software Foundation Django 6.1 before 6.1.2, 6.0 before 6.0.9, 5.2 before 5.2.18.

**Is there a fix for CVE-2026-77050?** Yes: fixed in Django 6.1.2, 6.0.9, 5.2.18. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-77050 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-77050?** Check whether you run Django Software Foundation Django at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Django 6.1.2, 6.0.9, 5.2.18

## Technical details

The vulnerability exists in django.utils.translation.get_supported_language_variant(), which caches language code variants as dictionary keys without enforcing limits on cache size or entry length. An attacker can send HTTP requests with many distinct, very long language codes (via Accept-Language headers or other translation-related parameters) to cause the in-memory cache to grow unbounded, consuming process memory until the service becomes unavailable. The vulnerability affects Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18, with potentially older unsupported versions also affected.

## Affected products

- Django Software Foundation Django 6.1 before 6.1.2, 6.0 before 6.0.9, 5.2 before 5.2.18

## Timeline

- 2026-10-06: disclosed
- 2026-10-06: patched

## References

- [https://pypi.org/project/Django/](https://pypi.org/project/Django/)
- [https://docs.djangoproject.com/en/dev/releases/security/](https://docs.djangoproject.com/en/dev/releases/security/)

## Related threats

- [Django GIS spatial reference string injection](https://junglewise.ai/threats/cve-2026-114582-an-issue-was-discovered-in-django-6-1-before-6-1-3-6-0-before-6)
- [Django SSRF in GeoJSON coordinate reference systems](https://junglewise.ai/threats/cve-2026-111362-an-issue-was-discovered-in-django-6-1-before-6-1-3-6-0-before-6)
- [Django log injection in BaseGeometryWidget.deserialize()](https://junglewise.ai/threats/cve-2026-111211-an-issue-was-discovered-in-django-6-1-before-6-1-3-6-0-before-6)
- [Django multipart parser excessive memory consumption via base64 Content-Transfer-Encoding](https://junglewise.ai/threats/cve-2026-108147-an-issue-was-discovered-in-django-6-1-before-6-1-3-6-0-4-before)
- [Django authorization bypass in BaseModelFormSet deletion](https://junglewise.ai/threats/cve-2026-87975-an-issue-was-discovered-in-django-6-1-before-6-1-2-6-0-before-6-0)