Vulnerability advisory

GHSA-w26r-rmm8-9c29

Django has an Improper Handling of Length Parameter Inconsistency

Published May 5, 2026Updated Sep 10, 2026OSV record ↗

Also known as BIT-django-2026-5766CVE-2026-5766PYSEC-2026-54

Severity

CVSS 3.xCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CVSS 4.0CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Affected versions

django PyPI

All django advisories →

Affected	Fixed in
`6.0` to before 6.0.5	`6.0.5`Advisories →
Also listed as affected (5) `6.0` `6.0.1` `6.0.2` `6.0.3` `6.0.4`
`5.2` to before 5.2.14	`5.2.14`Advisories →
Also listed as affected (14) `5.2` `5.2.1` `5.2.10` `5.2.11` `5.2.12` `5.2.13` `5.2.2` `5.2.3` `5.2.4` `5.2.5` `5.2.6` `5.2.7` `5.2.8` `5.2.9`

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

GHSA-w26r-rmm8-9c29

Affected versions

django PyPI

Description

References