Skip to main content
VulnerabilityPublished

CVE-2026-84429: djangoproject Django · Inefficient Algorithmic Complexity

Affects djangoproject DjangoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium · fixed in 6.1.2 : update djangoproject Django when convenient.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 and django to 6.1.2, 6.0.9 or 5.2.18.

Affected software

ProductAffectedFixed in
djangoprojectDjangoAffected
  • >=6.1 <6.1.2
Fixed in
  • 6.1.2
djangoprojectDjangoAffected
  • >=6.0 <6.0.9
Fixed in
  • 6.0.9
djangoprojectDjangoAffected
  • >=5.2 <5.2.18
Fixed in
  • 5.2.18
PyPIdjangopkg:pypi/djangoOther threatsAffected
  • >=6.1 <6.1.2
  • >=6.0 <6.0.9
  • >=5.2 <5.2.18
Fixed in
  • 6.1.2
  • 6.0.9
  • 5.2.18

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 5.2.18, 6.0.9, and 6.1.2 address this issue. Users should upgrade to these or later versions to remediate the vulnerability. No other mitigation or workaround is specified. Patch status is confirmed by the affectedVersions field indicating fixed versions as the exclusive upper bounds.

Description

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.

References

Community reviews

Loading reviews…