Description
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 would like to thank Kyle Agronick for reporting this issue.
Problem types
CWE-130: Improper Handling of Length Parameter Inconsistency
Product status
6.0 (python) before 6.0.5
6.0.5 (python)
5.2 (python) before 5.2.14
5.2.14 (python)
Timeline
| 2024-05-12: | Initial report received. |
| 2026-04-07: | Vulnerability confirmed. |
| 2026-05-05: | Security release issued. |
Credits
Kyle Agronick
Jacob Walls
Sarah Boyce
References
docs.djangoproject.com/en/dev/releases/security/ (Django security archive)
groups.google.com/g/django-announce (Django releases announcements)
www.djangoproject.com/weblog/2026/may/05/security-releases/ (Django security releases issued: 6.0.5 and 5.2.14)