CVE-2026-84429

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 4 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • 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.

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.http.parse_header_parameters() was subject to a potential denial-of-service attack due to quadratic time complexity when parsing a value with many separators inside a quoted parameter. An unauthenticated request could reach this parsing through headers such as Accept or Content-Type, for instance via the content negotiation performed by HttpRequest.accepts(). The per-call length limit does not bound the combined size of repeated headers. 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 Jisung Chae for reporting this issue.

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
39
EG Risk 39/100CISA SSVC

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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 6, 2026

Last Modified

October 6, 2026

Advisory Details (7)

Auto-updated Oct 6, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

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 6ecd66e09a38 (django/django)

Fix landed in django/django commit 6ecd66e09a38 — awaiting tagged release

https://github.com/django/django/commit/6ecd66e09a383be004a78a3a738ea9727ff07b0e
github_commit

commit 3d8f121695c2 (django/django)

Fix landed in django/django commit 3d8f121695c2 — awaiting tagged release

https://github.com/django/django/commit/3d8f121695c21234aff3071de0d38b6bd38c3f52
github_commit

commit de56deeabd4c (django/django)

Fix landed in django/django commit de56deeabd4c — awaiting tagged release

https://github.com/django/django/commit/de56deeabd4c48dfb5193f0001469d80102fb367
github_commit

commit 7ff7fcc05088 (django/django)

Fix landed in django/django commit 7ff7fcc05088 — awaiting tagged release

https://github.com/django/django/commit/7ff7fcc0508864a4bc39693128ace38b1e95a890
generic
https://groups.google.com/g/django-announce
generic

Archive of security issues | Django documentation | Django

https://docs.djangoproject.com/en/dev/releases/security/

Vendor Advisories for CVE-2026-84429(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-10 20:26 UTCEG score recompute
  2. 2026-10-10 20:26 UTCGHSA enrichment
  3. 2026-10-10 20:00 UTCEPSS rescore
  4. 2026-10-09 20:07 UTCEPSS rescore
  5. 2026-10-09 19:14 UTCGHSA enrichment
  6. 2026-10-08 18:05 UTCEG score recompute
  7. 2026-10-08 18:05 UTCGHSA enrichment
  8. 2026-10-08 17:13 UTCEPSS rescore
  9. 2026-10-07 23:48 UTCEPSS rescore
  10. 2026-10-07 16:57 UTCEG score recompute
  11. 2026-10-07 16:56 UTCGHSA enrichment
  12. 2026-10-06 14:31 UTCEG score recompute
  13. 2026-10-06 13:40 UTCEG score recompute
  14. 2026-10-06 13:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84429?
CVE-2026-84429 is a medium vulnerability 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.http.parseheaderparameters() was subject to a potential denial-of-service attack due to quadratic time complexity when parsing a value with many separators inside a quoted parameter. An…
When was CVE-2026-84429 disclosed?
CVE-2026-84429 was first published on October 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84429 actively exploited?
CVE-2026-84429 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-84429?
CVE-2026-84429 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-84429?
An upstream fix for CVE-2026-84429 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-84429 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-84429

Explore →

Is Your Infrastructure Affected by CVE-2026-84429?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs