CVE-2026-5766: Django Django Has An Improper Handling Vulnerability

MODERATE
Advisory Identifier: GHSA-w26r-rmm8-9c29
Share
CVSS 5.3
CWE-130
Published
Advisory Summary

CVE-2026-5766 is a MODERATE (CVSS 5.3) django has an improper handling vulnerability (CWE-130: Improper Handling of Length Parameter Inconsistency) affecting Django libraries in the PyPI ecosystem. The issue involves django has an improper handling of length parameter inconsistency. Remediation is available by upgrading affected packages to version 6.0.5, 5.2.14.

CVE-2026-5766 at a Glance

CVE Identifier CVE-2026-5766
GHSA Identifier GHSA-w26r-rmm8-9c29
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-130: Improper Handling of Length Parameter Inconsistency
Affected Product Django
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-5766

To remediate this vulnerability, upgrade all affected Django dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Django fixed: 6.0.5 
pip install Django>=6.0.5
Django fixed: 5.2.14 
pip install Django>=5.2.14
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show Django

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-5766, inspect your installed packages using pip:

pip show Django

Analyze the terminal output to locate any version of Django in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.0.5), your application is affected.

Note: The pip show Django command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-130: Improper Handling of Length Parameter Inconsistency, where the product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data. In Django, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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 thanks Kyle Agronick for reporting this issue.

CVE-2026-5766 Affected Django Versions

2 component(s)
Fixed Versions:
6.0.55.2.14
Product / Package Ecosystem Affected Versions Fixed Version
Django
pypi/Django
PyPI
≥ 6.0
< 6.0.5
6.0.5
Django
pypi/Django
PyPI
≥ 5.2
< 5.2.14
5.2.14

References

NVD — CVE-2026-5766 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-5766
Django Release RELEASE
https://docs.djangoproject.com/en/dev/releases/security
Django Source Repository REPOSITORY
https://github.com/django/django
Django Source Repository REPOSITORY
https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-54.yaml
groups.google.com/g/django-announce WEB
https://groups.google.com/g/django-announce
Django Release RELEASE
https://www.djangoproject.com/weblog/2026/may/05/security-releases

Frequently Asked Questions

What is CVE-2026-5766?
CVE-2026-5766 is a security vulnerability in Django involving Django has an Improper Handling of Length Parameter Inconsistency under CWE-130: Improper Handling of Length Parameter Inconsistency.
Which Django versions are affected?
Affected versions include releases prior to 6.0.5, 5.2.14 across affected packages: Django.
What version fixes CVE-2026-5766?
Upgrading to 6.0.5, 5.2.14 (or the latest patched release for your respective branch) resolves the vulnerability.
Is Django affected?
Yes, Django is affected in releases prior to 6.0.5, 5.2.14. Upgrade your dependency to 6.0.5, 5.2.14 or later.
What is the CVSS score of CVE-2026-5766?
CVE-2026-5766 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-5766?
CVE-2026-5766 is classified under CWE-130: Improper Handling of Length Parameter Inconsistency (The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.).
How can I check PyPI dependencies for CVE-2026-5766?
Run the dependency tree command: 'pip show Django'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-w26r-rmm8-9c29",
  "modified" : "2026-06-06T00:27:41Z",
  "published" : "2026-05-05T18:33:26Z",
  "aliases" : [ "CVE-2026-5766" ],
  "summary" : "Django has an Improper Handling of Length Parameter Inconsistency",
  "details" : "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.\n \nAs 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.\n\nDjango thanks Kyle Agronick for reporting this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS: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" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "Django"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.0"
      }, {
        "fixed" : "6.0.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "Django"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.2"
      }, {
        "fixed" : "5.2.14"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-5766"
  }, {
    "type" : "WEB",
    "url" : "https://docs.djangoproject.com/en/dev/releases/security"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/django/django"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-54.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://groups.google.com/g/django-announce"
  }, {
    "type" : "WEB",
    "url" : "https://www.djangoproject.com/weblog/2026/may/05/security-releases"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-130" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-08T22:14:39Z",
    "nvd_published_at" : "2026-05-05T16:16:17Z"
  }
}