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.
CVE-2026-77050
MEDIUMPre-NVD 5.35.3Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.3 from GitHub Security Advisory published 2026-10-06. A secondary CVSS source baseline 5.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMhigh confidence
- EG Risk
- 39EG Risk 39/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%The EG Score, 5.3 of 10.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release. - EPSS PROB
- 0.4%
- EPSS %ILE
- 30th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 6, 2026
Last Modified
October 6, 2026
Advisory Details (7)
Auto-updated Oct 6, 2026Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page
Django security releases issued: 6.1.2, 6.0.9, and 5.2.18 | Weblog | Django
https://www.djangoproject.com/weblog/2026/oct/06/security-releases/GitHub commit
commit 02a69e3791e3 (django/django)
Fix landed in django/django commit 02a69e3791e3 — awaiting tagged release
https://github.com/django/django/commit/02a69e3791e3df23d45ea4ea7e7fc489f0eef2beGitHub commit
commit 3d32ee80ae52 (django/django)
Fix landed in django/django commit 3d32ee80ae52 — awaiting tagged release
https://github.com/django/django/commit/3d32ee80ae52745d686bf94d3555000ddf073267GitHub commit
commit 7e878b0f8bd4 (django/django)
Fix landed in django/django commit 7e878b0f8bd4 — awaiting tagged release
https://github.com/django/django/commit/7e878b0f8bd42260903e6a0d38996a93b0474a0bGitHub commit
commit c88b304cc2d9 (django/django)
Fix landed in django/django commit c88b304cc2d9 — awaiting tagged release
https://github.com/django/django/commit/c88b304cc2d90fc37d3bd1f5f3829706fa6c13bcWeb page
Archive of security issues | Django documentation | Django
https://docs.djangoproject.com/en/dev/releases/security/Vendor Advisories for CVE-2026-77050(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-django | 3:3.2.19-1 ... 3:6.1~rc1-1 (113 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-django | 3:4.2.23-1 ... 3:6.1~rc1-1 (67 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-django | 3:4.2.23-1 ... 3:6.1~rc1-1 (64 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 25× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-12 15:37 UTCEG score recompute
- 2026-10-11 19:23 UTCEG score recompute
- 2026-10-11 16:39 UTCEG score recompute
- 2026-10-11 13:58 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-11 12:02 UTCEG score recompute
- 2026-10-11 12:02 UTCGHSA enrichmentGHSA-mxcg-2f2x-4q92 · GitHub CVSS 5.3
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-10 13:04 UTCEG score recompute
- 2026-10-10 13:04 UTCGHSA enrichmentGHSA-mxcg-2f2x-4q92 · GitHub CVSS 5.3
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-09 14:12 UTCEG score recompute
- 2026-10-09 14:11 UTCGHSA enrichmentGHSA-mxcg-2f2x-4q92 · GitHub CVSS 5.3
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-08 15:17 UTCEG score recompute
- 2026-10-08 15:17 UTCGHSA enrichmentGHSA-mxcg-2f2x-4q92 · GitHub CVSS 5.3
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-07 14:19 UTCEG score recompute
- 2026-10-07 14:19 UTCGHSA enrichmentGHSA-mxcg-2f2x-4q92 · GitHub CVSS 5.3
- 2026-10-06 15:27 UTCEG score recompute
- 2026-10-06 14:31 UTCEG score recompute
- 2026-10-06 13:40 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
- 2026-10-06 13:39 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:12:python-django
- CVE-2014-0474EG 10.0EPSS p92HIGH
- CVE-2026-4277EG 9.8CRITICAL
- CVE-2025-59681EG 9.8CRITICAL
- CVE-2023-31047EG 9.8CRITICAL
- CVE-2022-34265EG 9.8EPSS p99CRITICAL
- CVE-2022-28347EG 9.8CRITICAL
- CVE-2022-28346EG 9.8EPSS p97CRITICAL
- CVE-2020-7471EG 9.8EPSS p99CRITICAL
- CVE-2019-19844EG 9.8EPSS p99CRITICAL
- CVE-2019-14234EG 9.8EPSS p99CRITICAL
Frequently asked(5)
What is CVE-2026-77050?
CVE-2026-77050 is a medium-severity vulnerability; its CVE record was published on October 6, 2026. 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.getsupportedlanguage_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…
When was CVE-2026-77050 made public?
CVE-2026-77050 was made public on October 6, 2026: that is the date its CVE record's CNA, Django Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on October 6, 2026. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-77050 actively exploited?
CVE-2026-77050 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77050?
CVE-2026-77050 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77050?
An upstream fix for CVE-2026-77050 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-77050 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77050
Is Your Infrastructure Affected by CVE-2026-77050?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.