CVE-2026-5766 Potential denial-of-service vulnerability in ASGI requests via file upload limit bypass
Attackers can cause denial of service in Django ASGI applications by bypassing file upload memory limits via manipulated Content-Length headers.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-5766?
CVE-2026-5766 is a medium-severity denial of service vulnerability in Djangoproject Django, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-130
Which versions are affected by CVE-2026-5766?
6 open source packages ship an affected version, including django and Django. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django Bitnami | From 5.2.0 | 5.2.14, 6.0.5 |
django PyPI | From 5.2 | 5.2.14, 6.0.5 |
django PyPI | From 5.2 | 5.2.14 |
django PyPI | From 6.0 | 6.0.5 |
Django PyPI | From 5.2 | 5.2.14 |
Django PyPI | From 6.0 | 6.0.5 |
Products include Djangoproject Django.
How do I fix CVE-2026-5766?
Upgrade django to a fixed version for your release line: 5.2.14 or 6.0.5.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-5766 being exploited?
There is no known exploitation of CVE-2026-5766 in the wild and no public exploit code.
Other vulnerabilities in Djangoproject Django
- CVE-2026-4277 Privilege abuse in GenericInlineModelAdmin
- CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle
- CVE-2024-42005 Django SQL injection vulnerability
- CVE-2023-31047 Django bypasses validation when using one form field to upload multiple files
- CVE-2022-34265 Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection
Sources
Also known as BIT-django-2026-5766, DEBIAN-CVE-2026-5766, ECHO-35cc-781b-4acf, GHSA-w26r-rmm8-9c29, MINI-fgm7-pq75-6c3m, PYSEC-2026-54.