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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://docs.djangoproject.com/en/dev/releases/security/ Vendor Advisory
- https://www.djangoproject.com/weblog/2026/may/05/security-releases/ Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.3 · djangoprojectNVD modified 2026-10-26 19:10
Affected (CPE criteria) 1
cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
References 3
- https://docs.djangoproject.com/en/dev/releases/security/ Vendor Advisory
- https://groups.google.com/g/django-announce Third Party Advisory
- https://www.djangoproject.com/weblog/2026/may/05/security-releases/ Vendor Advisory