Skip to content
Fencer Vulns
medium 5.3

CVE-2026-73228 json

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 2026-08-11 2 mo ago modified 2026-10-24 15 d ago also GHSA-2m8g-3cmr-wg3w , PYSEC-2026-3827 , EUVD-2026-56887

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi djangorestframework 3.17.2
  • djangorestframework Debian 14 3.18.1+ds1-1

debian advisories DEBIAN-CVE-2026-73228

  • python-djangorestframework openSUSE Tumbleweed 3.18.0-2.1

opensuse advisories openSUSE-SU-2026:11625-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-73228 updated cvss 5.3

djangorestframework: Django REST framework: Denial of Service via oversized request bodies

  • Red Hat Ansible Automation Platform 2 automation-controller 4.7.15-2.el9ap, ansible-automation-platform-24/hub-rhel8, ansible-automation-platform-25/hub-rhel8, ansible-automation-platform-26/hub-rhel9, ansible-automation-platform-27/hub-rhel9, python-djangorestframework 3.14.0-1.el9ap, +18 more
    affected: workaround, no fix available, no fix planned “No mitigation is currently available for this vulnerability. Customers are advised to apply the available update when it becomes available.”
  • Red Hat Discovery 2 discovery/discovery-server-rhel9 Red Hat Satellite 6 python3-djangorestframework, satellite/iop-advisor-backend-rhel9, python-djangorestframework 3.14.0-1.el9ap, tfm-pulpcore-python-djangorestframework 3.12.4-4.el7pc
    affected: workaround, no fix available “No mitigation is currently available for this vulnerability. Customers are advised to apply the available update when it becomes available.”
  • Red Hat Update Infrastructure 4 for Cloud Providers python-djangorestframework 3.14.0-1.el9ap
    affected: workaround, no fix planned “No mitigation is currently available for this vulnerability. Customers are advised to apply the available update when it becomes available.”
  • Red Hat Update Infrastructure 5 rhui5/rhua-rhel9
    affected: workaround, no fix available “No mitigation is currently available for this vulnerability. Customers are advised to apply the available update when it becomes available.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/encode/django-rest-framework/security/advisories/GHSA-2m8g-3cmr-wg3w referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
pypi djangorestframework
<3.17.2
3.17.2

Affected products

  • encode django-rest-framework

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.