CVE-2026-33034: djangoproject Django · Unthrottled Resource Allocation
Affects djangoproject DjangoSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 6.0.4 : patch djangoproject Django soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 55% 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:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Apr 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 24 Oct 2026.
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
| Fixed in
|
| djangoprojectDjango | Affected
| Fixed in
|
| djangoprojectDjango | Affected
| Fixed in
|
PyPIdjangopkg:pypi/djangoOther threats | Affected
| Fixed in
|
PyPIdjangopkg:pypi/djangoOther 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
If you cannot patch yet, consider implementing request size validation at upstream proxies or web servers to limit request body sizes and prevent resource exhaustion.
Description
A vulnerability in Django versions 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30 allows ASGI requests with missing or understated Content-Length headers to bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit.