Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Djangoproject | Django | >= 5.2, < 5.2.14 |
Related Weaknesses (CWE)
References
- https://docs.djangoproject.com/en/dev/releases/security/Vendor Advisory
- https://groups.google.com/g/django-announceThird Party Advisory
- https://www.djangoproject.com/weblog/2026/may/05/security-releases/Vendor Advisory
FAQ
What is CVE-2026-5766?
CVE-2026-5766 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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 l...
How severe is CVE-2026-5766?
CVE-2026-5766 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-5766?
Check the references section above for vendor advisories and patch information. Affected products include: Djangoproject Django.