Skip to main content

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. (CVE-2026-77050)

0
Medium
Published: 10/06/2026 (10/06/2026, 15:32:00 UTC)
Source: GCVE Database

Description

A denial-of-service vulnerability exists in Django versions prior to 6.1.2, 6.0.9, and 5.2.18. The function django.utils.translation.get_supported_language_variant() can be exploited by processing many distinct, very long language codes, which are cached in memory and cause increased memory consumption leading to potential service disruption.

CVSS v3.1

Score 5.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected software

django
pkg:pypi/django
Affected versions
>=6.0.0 <6.0.9>=6.1.0 <6.1.2

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/06/2026, 17:03:59 UTC

Technical Analysis

CVE-2026-77050 affects Django versions 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18. The vulnerability arises from the get_supported_language_variant() function in django.utils.translation, which caches language codes as keys in memory. When many distinct and very long language codes are processed, this cache grows significantly, potentially causing a denial-of-service condition due to excessive memory consumption. Earlier unsupported Django series such as 5.1.x, 5.0.x, and 4.2.x were not evaluated but may also be affected. The issue was reported by Gleb Lizunov.

Potential Impact

The vulnerability allows an attacker to cause a denial-of-service by exhausting server memory through the submission of many distinct, very long language codes. This does not affect confidentiality or integrity but impacts availability by potentially crashing or severely degrading the Django application.

Mitigation Recommendations

Official fixes are available in Django versions 6.1.2, 6.0.9, and 5.2.18. Users should upgrade to these or later versions to remediate the vulnerability. No vendor advisory content was provided beyond version information, so patch status is confirmed by the version numbers stated. No additional mitigations are specified.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-mxcg-2f2x-4q92
Osv Schema Version
1.4.0
Aliases
["CVE-2026-77050"]
Database Specific Severity
MODERATE
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ac523702cdf04f656c4bf17

Added to database: 10/06/2026, 16:36:00 UTC

Last enriched: 10/06/2026, 17:03:59 UTC

Last updated: 10/07/2026, 03:48:07 UTC

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses