CVE-2026-33034

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated Content-Length header could bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading HttpRequest.body, allowing remote attackers to load an unbounded request body into memory.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Superior for reporting this issue.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2026-33034 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.0.4, 5.2.13, 4.2.30); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-33034? CVE-2026-33034 is a high-severity allocation of resources without limits or throttling vulnerability in Django (pip), affecting versions >= 6.0, < 6.0.4. It is fixed in 6.0.4, 5.2.13, 4.2.30. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is CVE-2026-33034? CVE-2026-33034 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of Django are affected by CVE-2026-33034? Django (pip) versions >= 6.0, < 6.0.4 is affected.
4. Is there a fix for CVE-2026-33034? Yes. CVE-2026-33034 is fixed in 6.0.4, 5.2.13, 4.2.30. Upgrade to this version or later.
5. Is CVE-2026-33034 exploitable, and should I be worried? Whether CVE-2026-33034 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33034 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33034?
   • Upgrade Django to 6.0.4 or later
   • Upgrade Django to 5.2.13 or later
   • Upgrade Django to 4.2.30 or later