django
Affected
- introduced
6.0, fixed6.0.5(ecosystem)
Fixed versions
6.0.5
Fix
- Fixed version
6.0.5pip install --upgrade django==6.0.5
Advisory
Also known as: BIT-django-2026-5766, CVE-2026-5766, PYSEC-2026-54
Django has an Improper Handling of Length Parameter Inconsistency
An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. ASGI requests with a missing or understated Content-Length header can bypass the FILE_UPLOAD_MAX_MEMORY_SIZE limit, potentially loading large files into memory and causing service degradation.
As a reminder, Django expects a limit to be configured at the web server level rather than solely relying on FILE_UPLOAD_MAX_MEMORY_SIZE. 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 thanks Kyle Agronick for reporting this issue.
Medium Basis: The source's own band: MODERATE
6.0, fixed 6.0.5 (ecosystem)6.0.5
6.0.5pip install --upgrade django==6.0.55.2, fixed 5.2.14 (ecosystem)5.2.14
5.2.14pip install --upgrade django==5.2.14Fix 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