PT-2026-39154 · Bitnami · Django
Published
2026-05-08
·
Updated
2026-05-08
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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. Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Django