VulnerabilityPublished 7 Apr 2026

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

Affects djangoproject DjangoSource CVE Database V5

Compare

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

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.0.4, 5.2.13, 4.2.30

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Django and django to 6.0.4, 5.2.13 or 4.2.30.

Affected software

Product	Affected	Fixed in
djangoprojectDjango	Affected >=6.0 <6.0.4	Fixed in 6.0.4
djangoprojectDjango	Affected >=5.2 <5.2.13	Fixed in 5.2.13
djangoprojectDjango	Affected >=4.2 <4.2.30	Fixed in 4.2.30
PyPIdjango`pkg:pypi/django`Other threats	Affected =4.2 =5.2 =6.0	Fixed in–
PyPIdjango`pkg:pypi/django`Other threats	Affected >=6.0 <6.0.4 >=5.2 <5.2.13 >=4.2 <4.2.30	Fixed in 6.0.4 5.2.13 4.2.30

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, consider limiting or filtering multipart upload requests with suspicious 'Content-Transfer-Encoding: base64' headers containing excessive whitespace if feasible. Monitor for unusual performance degradation related to multipart uploads. Avoid relying on generic mitigations unless specifically recommended by the vendor.

Description

CVE-2026-33033 is a medium severity vulnerability in Django versions prior to 6.0.4, 5.2.13, and 4.2.30. It involves inefficient algorithmic complexity in the MultiPartParser component, where remote attackers can degrade server performance by submitting multipart uploads with 'Content-Transfer-Encoding: base64' containing excessive whitespace. This issue affects specific supported versions of Django and potentially earlier unsupported versions.

Impact

The impact is a denial of service condition through performance degradation (availability impact) without affecting confidentiality or integrity. Attackers can remotely cause the Django server to consume excessive resources when processing specially crafted multipart uploads, potentially leading to service slowdown or unavailability. There is no indication of data compromise or code execution.

CWE-407Inefficient Algorithmic Complexity (opens in a new tab)
Class weaknessLikelihood of exploit: Low
An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Apr 2026, 15:59 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-407

Technical details

References

Community reviews

Related threats