Intel

AIKIDO-2026-616781

django is vulnerable to Denial of Service (DoS)

CVE-2026-84429Published Oct 16, 2026
October 16, 2026

50

CVE Score

Medium

Denial of Service (DoS)

Are you affected? Scan for Free

TL;DR

Django's django.utils.http.parse_header_parameters() parsed Content-Type-like header values (such as Accept or Content-Type) using a custom _parseparam() generator that rescanned the remaining string for the next unescaped semicolon on every iteration, giving quadratic time complexity when a quoted parameter value contained many semicolon separators. An unauthenticated attacker could trigger this parsing path via ordinary HTTP headers processed during content negotiation (e.g. HttpRequest.accepts()), and the existing MAX_HEADER_LENGTH per-call limit did not bound the cost of repeated headers, enabling a denial-of-service. The fix replaces the custom parser with Python's email.message.Message-based parameter parsing, eliminating the quadratic rescanning behavior.

How do I fix this?

Upgrade the django library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you parse request headers such as Accept or Content-Type through parse_header_parameters() or HttpRequest.accepts().

Package

Versions

5.2 - 5.2.17

Fixed in 5.2.18

6.0 - 6.0.8

Fixed in 6.0.9

6.1 - 6.1.1

Fixed in 6.1.2

Background info

django is vulnerable to Denial of Service (DoS) in versions 6.1 - 6.1.1, 6.0 - 6.0.8 and 5.2 - 5.2.17.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea