CVE-2026-33034
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- docs.djangoproject.com/en/dev/releases/security/
- groups.google.com/g/django-announce
- www.djangoproject.com/weblog/2026/apr/07/security-releases/
- nvd.nist.gov/vuln/detail/CVE-2026-33034
- docs.djangoproject.com/en/dev/releases/security
- www.djangoproject.com/weblog/2026/apr/07/security-releases
- github.com/advisories/GHSA-933h-hp56-hf7m
- github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-49.yaml
- nvd.nist.gov/vuln/detail/CVE-2026-33034
- cve.org/CVERecord?id=CVE-2026-33034
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.