How severe is CVE-2026-5766?

CVE-2026-5766 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.

Is CVE-2026-5766 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-5766?

CVE-2026-5766 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-5766?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-5766 have an EU (EUVD) identifier?

Yes. CVE-2026-5766 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-27381.

When was CVE-2026-5766 published?

CVE-2026-5766 was published on 2026-05-05 and last updated on 2026-06-17.

CVE-2026-5766

CVE-2026-5766 is a medium-severity vulnerability in Djangoproject Django with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-130.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
CVSS v4: 6.3
EPSS exploit prediction: 0% (34th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-27381
Weakness: CWE-130
Affected product: Djangoproject Django
Published: 2026-05-05
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2026-5766?: 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.
How severe is CVE-2026-5766?: CVE-2026-5766 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.
Is CVE-2026-5766 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-5766?: CVE-2026-5766 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-5766?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-5766 have an EU (EUVD) identifier?: Yes. CVE-2026-5766 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-27381.
When was CVE-2026-5766 published?: CVE-2026-5766 was published on 2026-05-05 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*

More vulnerabilities in Djangoproject Django

CVE-2014-0474 — Critical (CVSS 10.0): The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11,…
CVE-2026-4277 — Critical (CVSS 9.8): An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model…
CVE-2024-53908 — Critical (CVSS 9.8): An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the…
CVE-2023-31047 — Critical (CVSS 9.8): In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using…
CVE-2022-34265 — Critical (CVSS 9.8): An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions…
CVE-2022-28347 — Critical (CVSS 9.8): A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0…

All CVEs affecting Djangoproject Django →

Other CWE-130 vulnerabilities

CVE-2022-2714 — Critical (CVSS 9.8): Improper Handling of Length Parameter Inconsistency in GitHub repository francoisjacquet/rosariosis prior to 10.0.
CVE-2026-9054 — Critical (CVSS 9.2): An attacker sending tcp, il, rudp, rudp, or gre packets with a length less than the header size would trigger a kernel…
CVE-2022-1543 — High (CVSS 8.8): Improper handling of Length parameter in GitHub repository erudika/scoold prior to 1.49.4. When the text size is large…
CVE-2026-3868 — High (CVSS 8.7): An improper handling of the length parameter inconsistency vulnerability has been identified in Moxa’s Secure…
CVE-2026-5367 — High (CVSS 8.6): A flaw was found in OVN (Open Virtual Network). A remote attacker, by sending crafted DHCPv6 (Dynamic Host…
CVE-2022-20870 — High (CVSS 8.6): A vulnerability in the egress MPLS packet processing function of Cisco IOS XE Software for Cisco Catalyst 3650,…

Browse all CWE-130 vulnerabilities →