Django REST framework: Potential bypass of Django `DATA_UPLOAD_MAX_MEMORY_SIZE` when parsing oversized JSON and urlencoded request bodies via DRF `request.data` — GHSA-2M8G-3CMR-WG3W
GitHub · GitHub · GHSA-2M8G-3CMR-WG3W
ID
GHSA-2M8G-3CMR-WG3W
GHSA-2M8G-3CMR-WG3W
Date
Source
GitHub
GitHub
Vendor
GitHub
GitHub
Threat
medium
medium
CVSS
5.3
5.3
EPSS
0.00321
0.00321
Summary
## Summary While investigating Django REST Framework's request parsing behavior, I identified that DRF's high-level `request.data` parsing appears to bypass Django's configured `DATA_UPLOAD_MAX_MEMORY_SIZE` protection for `application/json` and `application/x-www-form-urlencoded` request bodies. In the tested configurations, Django correctly raises `RequestDataTooBig` when applications access `request.body` or…
Timeline
- Published by source
- 2026-09-01
Risk context
- Reported severity or threat level: medium.
- Reported CVSS score: 5.3 out of 10.
- Reported EPSS value: 0.00321.
- Review exposure for the affected product or family: pip: djangorestframework.
Product
pip: djangorestframework
What to do
General, cautious steps (verify details in the official source):
- Review exposure and plan remediation based on risk and environment.
- Identify affected product versions in your inventory and verify whether you are impacted.
- Apply vendor patches/updates or recommended mitigations as soon as available.
- Read the official advisory for exact affected versions and remediation steps.
Official advisory
Evidence and provenance
- Canonical advisory ID
- GHSA-2M8G-3CMR-WG3W
- Source
- GitHub
- Vendor
- GitHub
- Published by source
- 2026-09-01
- Last source activity
- 2026-09-01
- Additional identifiers
- CVE-2026-73228
- Curated by
- hlukh.ch
Related advisories and connections
These advisories are connected by shared CVE, product, vendor, source, or time signals.