Is CVE-2026-33034 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-33034 being exploited in the wild.

How severe is CVE-2026-33034?

High severity, with a CVSS score of 7.5, published 7 April 2026.

Which products and versions are affected?

Django (PyPI) ECOSYSTEM:introduced=4.2,fixed=4.2.30,introduced=5.2,fixed=5.2.13,introduced=6.0,fixed=6.0.4, ECOSYSTEM:introduced=6.0,fixed=6.0.4.

Is there a fix for CVE-2026-33034?

Yes. Django (PyPI): upgrade to 6.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-33034 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-33034?

Check whether you run Djangoproject Django or Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33034: Django memory limit bypass in ASGI requests

CVE-2026-33034 · Severity: high · CVSS 7.5 · Published 2026-04-07

A vulnerability in the Django web framework could allow an attacker to crash a server by sending specially crafted web requests. By omitting or misstating the size of an uploaded file, an attacker can bypass security limits and force the server to load an unlimited amount of data into its memory. This can lead to a denial-of-service condition, making the website or application unavailable to legitimate users.

Technologies: Djangoproject Django, Django (PyPI). Vendors: Djangoproject, PyPI.

Quick answers

Is CVE-2026-33034 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-33034 being exploited in the wild.
How severe is CVE-2026-33034?: High severity, with a CVSS score of 7.5, published 7 April 2026.
Which products and versions are affected?: Django (PyPI) ECOSYSTEM:introduced=4.2,fixed=4.2.30,introduced=5.2,fixed=5.2.13,introduced=6.0,fixed=6.0.4, ECOSYSTEM:introduced=6.0,fixed=6.0.4.
Is there a fix for CVE-2026-33034?: Yes. Django (PyPI): upgrade to 6.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33034 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-33034?: Check whether you run Djangoproject Django or Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Django (PyPI): upgrade to 6.0.4 or later
```
pip install "Django>=6.0.4"
```

Technical details

A resource exhaustion vulnerability exists in Django's handling of ASGI requests. When reading 'HttpRequest.body', the framework fails to properly enforce the 'DATA_UPLOAD_MAX_MEMORY_SIZE' limit if the 'Content-Length' header is missing or provides an understated value. A remote, unauthenticated attacker can exploit this by sending a large request body, causing the server to allocate unbounded memory. This leads to a Denial of Service (DoS) via memory exhaustion. The issue is fixed in Django versions 6.0.4, 5.2.13, and 4.2.30.

Affected products

Django Software Foundation Django >= 6.0, < 6.0.4; >= 5.2, < 5.2.13; >= 4.2, < 4.2.30

Identifiers

CVE-2026-33034
GHSA-933h-hp56-hf7m
PYSEC-2026-49

Timeline

2026-04-07: disclosed
2026-04-07: advisory
2026-04-07: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.