CVE-2026-5766

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.

Predictions

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

References

• https://docs.djangoproject.com/en/dev/releases/security/
• https://groups.google.com/g/django-announce
• https://www.djangoproject.com/weblog/2026/may/05/security-releases/
• https://nvd.nist.gov/vuln/detail/CVE-2026-5766
• https://docs.djangoproject.com/en/dev/releases/security
• https://github.com/django/django
• https://www.djangoproject.com/weblog/2026/may/05/security-releases
• https://www.suse.com/security/cve/CVE-2026-5766.html
• https://security-tracker.debian.org/tracker/CVE-2026-5766
• https://github.com/advisories/GHSA-w26r-rmm8-9c29

CWEs

CWE-130