CVE-2026-5766

Name	CVE-2026-5766
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.
Source	CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
Debian Bugs	1135755

Vulnerable and fixed packages

The table below lists information on source packages.

Source Package	Release	Version	Status
python-django (PTS)	bullseye	2:2.2.28-1~deb11u2	vulnerable
	bullseye (security)	2:2.2.28-1~deb11u12	vulnerable
	bookworm, bookworm (security)	3:3.2.25-0+deb12u2	vulnerable
	trixie (security), trixie	3:4.2.28-0+deb13u1	vulnerable
	forky	3:4.2.30-1	vulnerable
	sid	3:5.2.14-2	fixed

The information below is based on the following data on fixed versions.

Package	Type	Release	Fixed Version	Urgency	Origin	Debian Bugs
python-django	source	(unstable)	3:5.2.14-1			1135755

Notes

[trixie] - python-django <no-dsa> (Minor issue)
[bookworm] - python-django <no-dsa> (Minor issue)
[bullseye] - python-django <no-dsa> (Minor issue)
https://www.djangoproject.com/weblog/2026/may/05/security-releases/
Fixed by: https://github.com/django/django/commit/2ec27eda3ba6c14f0856e6e3eb1df07c41fd95e6 (5.2.14)