CVE-2026-84429: Python django · 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
Affects python-djangoSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium · fixed in 6.1.2 : update python-django when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.1.2, 6.0.9, 5.2.18
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade django to 6.1.2, 6.0.9 or 5.2.18.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIdjangopkg:pypi/djangoOther threats | Affected
| Fixed in
|
Ubuntu Pro 14.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=esm-infra-legacy/trustyOther threats | Affected
| Fixed in– |
Ubuntu Pro 16.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=esm-infra-legacy/xenialOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=esm-infra/bionicOther threats | Affected
| Fixed in– |
Ubuntu Pro 20.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=esm-infra/focalOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSpython-djangopkg:deb/ubuntu/python-django?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Fixed versions are available: Django 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 contradicts this; therefore, upgrading is the recommended mitigation.
Description
A denial-of-service vulnerability exists in Django versions prior to 6.1.2, 6.0.9, and 5.2.18. The flaw is in the django.utils.http.parse_header_parameters() function, which can exhibit quadratic time complexity when parsing headers with many separators inside quoted parameters. This can be triggered by unauthenticated requests using headers such as Accept or Content-Type, potentially causing service disruption.
References
- nvd.nist.gov/vuln/detail/CVE-2026-84429 (opens in a new tab)
- github.com/django/django/commit/3d8f121695c21234aff3071de0d38b6bd38c3f52 (opens in a new tab)
- github.com/django/django/commit/6ecd66e09a383be004a78a3a738ea9727ff07b0e (opens in a new tab)
- github.com/django/django/commit/7ff7fcc0508864a4bc39693128ace38b1e95a890 (opens in a new tab)
- github.com/django/django/commit/de56deeabd4c48dfb5193f0001469d80102fb367 (opens in a new tab)
- docs.djangoproject.com/en/dev/releases/security (opens in a new tab)
- groups.google.com/g/django-announce (opens in a new tab)
- djangoproject.com/weblog/2026/oct/06/security-releases (opens in a new tab)
- ubuntu.com/security/CVE-2026-84429 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-84429 (opens in a new tab)
- djangoproject.com/weblog/2026/oct/06/security-releases/ (opens in a new tab)