Home

Description

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.

PUBLISHED Reserved 2026-03-17 | Published 2026-04-07 | Updated 2026-04-07 | Assigner DSF

Problem types

CWE-770: Allocation of Resources Without Limits or Throttling

Product status

Default status
unaffected

6.0 (semver) before 6.0.4
affected

6.0.4 (semver)
unaffected

5.2 (semver) before 5.2.13
affected

5.2.13 (semver)
unaffected

4.2 (semver) before 4.2.30
affected

4.2.30 (semver)
unaffected

Timeline

2026-02-24:Initial report received.
2026-03-17:Vulnerability confirmed.
2026-04-07:Security release issued.

Credits

Superior reporter

Natalia Bidart remediation developer

Jacob Walls coordinator

References

docs.djangoproject.com/en/dev/releases/security/ (Django security archive) vendor-advisory

groups.google.com/g/django-announce (Django releases announcements) mailing-list

www.djangoproject.com/weblog/2026/apr/07/security-releases/ (Django security releases issued: 6.0.4, 5.2.13, and 4.2.30) vendor-advisory

cve.org (CVE-2026-33034)

nvd.nist.gov (CVE-2026-33034)

Download JSON