Skip to content
fr Sign in
5.3 Medium

CVE-2026-5766 An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14

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.

Affected products and versions

Product Affected versions Fixed in
Django 6.0 6.0 → < 6.0.5 6.0.5
Django 5.2 5.2 → < 5.2.14 5.2.14

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Django

The 62 CVEs of Django →
CVE-2026-114582 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 5.3 Medium CVE-2026-113733 An issue was discovered in Django 6.1 before 6.1.3 and 6.0 before 6.0.10 2.2 Low CVE-2026-113593 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 3.1 Low CVE-2026-111362 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 5.3 Medium
Track this CVE