CVE-2026-84429: CWE-407: Inefficient Algorithmic Complexity in djangoproject Django
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.
CVSS v3.1
Score 5.3medium
Affected software
djangoproject
Django
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises from the django.utils.http.parse_header_parameters() function's handling of HTTP header parameters. When parsing headers with many separators inside quoted parameters, the function exhibits quadratic time complexity, which can be exploited to cause a denial-of-service by exhausting server resources. This can be triggered by unauthenticated requests through headers like Accept or Content-Type, for example during content negotiation via HttpRequest.accepts(). Affected versions include Django 5.2 prior to 5.2.18, 6.0 prior to 6.0.9, and 6.1 prior to 6.1.2. The vulnerability is tracked as CWE-407 (Inefficient Algorithmic Complexity).
Potential Impact
An attacker can cause a denial-of-service condition by sending crafted HTTP headers that trigger inefficient parsing in Django, potentially degrading or disrupting service availability. There is no impact on confidentiality or integrity. The attack requires no authentication and can be performed remotely over the network.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- DSF
- Date Reserved
- 2026-09-01T18:34:27.131Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ac4fc562cdf04f656b4d696
Added to database: 10/06/2026, 13:49:10 UTC
Last enriched: 10/06/2026, 14:04:52 UTC
Last updated: 10/07/2026, 03:48:07 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.