Django up to 4.2.29/5.2.12/6.0.3 Request Body HttpRequest.body allocation of resources

Summaryinfo

A vulnerability classified as problematic has been found in Django up to 4.2.29/5.2.12/6.0.3. Impacted is an unknown function of the component Request Body Handler. Performing a manipulation of the argument HttpRequest.body results in allocation of resources. This vulnerability is reported as CVE-2026-33034. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Django up to 4.2.29/5.2.12/6.0.3. It has been classified as problematic. This affects some unknown processing of the component Request Body Handler. The manipulation of the argument HttpRequest.body with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. The summary by CVE is:

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit when reading `HttpRequest.body`, allowing remote attackers to load an unbounded request body into memory. 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 Superior for reporting this issue.

It is possible to read the advisory at docs.djangoproject.com. This vulnerability is uniquely identified as CVE-2026-33034 since 03/17/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 305750 (Python Library Django 4.2.x < 4.2.30 / 5.2.x < 5.2.13 / 6.0.x < 6.0.4 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.2.30, 5.2.13 or 6.0.4 eliminates this vulnerability. The upgrade is hosted for download at docs.djangoproject.com.

The vulnerability is also documented in the databases at Tenable (305750) and CERT Bund (WID-SEC-2026-1002). Be aware that VulDB is the high quality source for vulnerability data.

Affected

• Ubuntu Linux
• Open Source Django

Productinfo

Type

• Content Management System

Name

• Django

Version

• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.2.9
• 4.2.10
• 4.2.11
• 4.2.12
• 4.2.13
• 4.2.14
• 4.2.15
• 4.2.16
• 4.2.17
• 4.2.18
• 4.2.19
• 4.2.20
• 4.2.21
• 4.2.22
• 4.2.23
• 4.2.24
• 4.2.25
• 4.2.26
• 4.2.27
• 4.2.28
• 4.2.29
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7
• 5.2.8
• 5.2.9
• 5.2.10
• 5.2.11
• 5.2.12
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion