CVE-2026-73228

Django REST framework: Potential bypass of Django `DATA_UPLOAD_MAX_MEMORY_SIZE` when parsing oversized JSON and urlencoded request bodies via DRF `request.data`

Published Aug 11, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Django REST framework is a toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework's request.data parsing in rest_framework/request.py Request._parse() passes the underlying HttpRequest stream to JSONParser and FormParser for application/json and application/x-www-form-urlencoded bodies, bypassing Django's DATA_UPLOAD_MAX_MEMORY_SIZE protection and allowing oversized request bodies to consume additional memory and CPU. This issue is fixed in version 3.17.2.

Analysis

AI-generated

Technical impact

Django REST Framework's request.data parsing bypasses the Django setting DATA_UPLOAD_MAX_MEMORY_SIZE when handling application/json or application/x-www-form-urlencoded bodies, allowing an attacker to send oversized payloads that consume more memory and CPU than intended. This uncontrolled resource consumption can lead to denial of service by exhausting server resources, as documented under CWE-400 and CWE-770.

Affected Systems

Encode’s Django REST Framework, version 3.17.1 and earlier, is affected. The vulnerability exists in any deployment of DRF that uses its default request.data parser prior to the fix introduced in 3.17.2.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity, while the EPSS score of less than 1% suggests a low likelihood of widespread exploitation. The vulnerability can be triggered by a remote attacker sending a large JSON or form-encoded payload over HTTP, typically without needing authentication. The issue is not listed in CISA's KEV catalog, further indicating limited real-world exploitation to date.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Django REST Framework to 3.17.2 or later.
  • Deploy the updated library in all environments that serve API requests.
  • As a temporary measure, configure upstream web servers (such as Nginx or Apache) to limit request body size (e.g., client_max_body_size) or implement custom middleware to enforce Django’s DATA_UPLOAD_MAX_MEMORY_SIZE before DRF processes the request.

Generated by OpenCVE AI on August 12, 2026 at 20:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-2m8g-3cmr-wg3w Django REST framework: Potential bypass of Django `DATA_UPLOAD_MAX_MEMORY_SIZE` when parsing oversized JSON and urlencoded request bodies via DRF `request.data`
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Encode
Encode django Rest Framework
Vendors & Products Encode
Encode django Rest Framework
Type Values Removed Values Added
Description Django REST framework is a toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework's request.data parsing in rest_framework/request.py Request._parse() passes the underlying HttpRequest stream to JSONParser and FormParser for application/json and application/x-www-form-urlencoded bodies, bypassing Django's DATA_UPLOAD_MAX_MEMORY_SIZE protection and allowing oversized request bodies to consume additional memory and CPU. This issue is fixed in version 3.17.2.
Title Django REST framework: Potential bypass of Django `DATA_UPLOAD_MAX_MEMORY_SIZE` when parsing oversized JSON and urlencoded request bodies via DRF `request.data`
Weaknesses CWE-400
CWE-770
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 13, 2026, 2:07 PM
Reserved
Aug 11, 2026, 2:41 PM
Status
Awaiting Analysis
Published
Aug 11, 2026, 7:18 PM
Modified
Oct 24, 2026, 3:10 PM
Severity
Moderate
Public date
Aug 11, 2026, 6:54 PM