django
Affected
- introduced
6.0, fixed6.0.4(ecosystem)
Fixed versions
6.0.4
Fix
- Fixed version
6.0.4pip install --upgrade django==6.0.4
Advisory
Also known as: BIT-django-2026-33034, CVE-2026-33034, PYSEC-2026-49
Django: SGI requests with a missing or understated Content-Length header could bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit
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.
High Basis: The source's own band: HIGH
6.0, fixed 6.0.4 (ecosystem)6.0.4
6.0.4pip install --upgrade django==6.0.45.2, fixed 5.2.13 (ecosystem)5.2.13
5.2.13pip install --upgrade django==5.2.134.2, fixed 4.2.30 (ecosystem)4.2.30
4.2.30pip install --upgrade django==4.2.30Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0