NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2026-5766: Django has an Improper Handling of Length Parameter Inconsistency

mediumCVSS 4.0 6.3 · 3.1 5.3GHSA-w26r-rmm8-9c29

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 FILEUPLOADMAXMEMORYSIZE 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 FILEUPLOADMAXMEMORYSIZE.

Published May 5, 2026 · Updated Jun 6, 2026

Affected packages

Django

Ecosystem
PyPI
Affected
>= 6.0, < 6.0.5
Fixed in
6.0.5
Check
pip show Django

Django

Ecosystem
PyPI
Affected
>= 5.2, < 5.2.14
Fixed in
5.2.14
Check
pip show Django

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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 thanks Kyle Agronick for reporting this issue.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More PyPI vulnerabilities

All PyPI entries