Vulnerability advisory

CVE-2026-5766

Potential denial-of-service vulnerability in ASGI requests via file upload limit bypass

Published May 5, 2026Updated Oct 28, 2026OSV record ↗

Also known as BIT-django-2026-5766GHSA-w26r-rmm8-9c29PYSEC-2026-54

Severity

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

Repository

Affected commits	Fixed by commit
GIT github.com/django/django ↗
9e7cc2b628fe8fd3895986af9b7fc9525034c1b0 to before 024c26b1e77ea5b1b158265167ade47927a64c06	`024c26b1e77ea5b1b158265167ade47927a64c06`
36b5f39d9372147f0e758f590e35ee2b2bc317dd to before 8f8ad09659d728423a00e0a3b5f16da5c3a38e24	`8f8ad09659d728423a00e0a3b5f16da5c3a38e24`
Also listed as affected (19) `5.2.13` `6.0.4` `5.2.12` `6.0.3` `5.2.11` `6.0.2` `6.0.1` `5.2.10` `6.0` `5.2.9` `5.2.8` `5.2.7` `5.2.6` `5.2.5` `5.2.4` `5.2.3` `5.2.2` `5.2.1` `5.2`

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.

CVE-2026-5766

Affected versions

Repository

Description

References