CVE-2026-5766
An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- docs.djangoproject.com/en/dev/releases/security/
- groups.google.com/g/django-announce
- www.djangoproject.com/weblog/2026/may/05/security-releases/
- nvd.nist.gov/vuln/detail/CVE-2026-5766
- docs.djangoproject.com/en/dev/releases/security
- www.djangoproject.com/weblog/2026/may/05/security-releases
- github.com/advisories/GHSA-w26r-rmm8-9c29
- github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-54.yaml
- nvd.nist.gov/vuln/detail/CVE-2026-5766
- cve.org/CVERecord?id=CVE-2026-5766
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.