CVEvulnerability
CVE-2026-5766
6.3 MEDIUM
Official page ↗
- Status
- Analyzed
- Published
- 2026-05-05
- Last modified
- 2026-10-26
- Assigner
- 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
- CVSS 4.0 (6a34fbeb-21d4-45e7-8e0a-62b95bc12c92)
- 6.3 MEDIUM — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- CVSS 3.1 (6a34fbeb-21d4-45e7-8e0a-62b95bc12c92)
- 5.3 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Weaknesses
- CWE-130
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.
Affected configurations
• djangoproject django (>= 5.2 < 5.2.14)
• djangoproject django (>= 6.0 < 6.0.5)
Related
Weakness · CWE (1)
- CWE-130 Improper Handling of Length Parameter Inconsistency weakness
References
- 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