CVE-2026-5766
Django has an Improper Handling of Length Parameter Inconsistency
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.
How to fix CVE-2026-5766
To remediate CVE-2026-5766, upgrade the affected package to a fixed version below.
- —upgrade to 5.2.14 or later
- —no fix listed
- —upgrade to 6.0.5 or later
- —upgrade to 5.2.14 or later
Is CVE-2026-5766 being exploited?
Low — EPSS is 0.1%, meaning exploitation activity has not been observed at scale.
Affected packages (4)
- >= 5.2.0, < 5.2.14, >= 6.0.0, < 6.0.5
- from 0
- >= 6.0, < 6.0.5
- >= 5.2, < 5.2.14, >= 6.0, < 6.0.5
CVSS scores
| Source | Version | Severity | Vector |
|---|---|---|---|
| osv | CVSS 4.0 | — | 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 |
| osv | CVSS 3.1 | MEDIUM5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |