ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-114136

Django REST framework is a toolkit for building Web APIs.

Published Oct 21, 2026 · catalog updated Oct 22, 2026 · Django REST framework is

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-114136. EPSS is 0.50%. Act only if a listed version of Django REST framework is is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Django REST framework is).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.50%
Remediation
Version ranges on file
Affected products
PyPI djangorestframework · package pip · pip djangorestframework · pypi djangorestframework

### Summary An unauthenticated attacker can defeat Django's limit and force a worker process to allocate arbitrary memory, by naming a compression codec in the Content-Type charset parameter. A 108-byte request body produces a 50,331,648-character value inside the view, an amplification factor of 466,033, and grows process peak RSS by about 97 MiB. No application configuration is required beyond DRF's default parser set; the endpoint only has to accept a JSON body. ### Details decodes the request body with the charset the client supplied on the Content-Type header: Of the roughly 455 codec names resolves on CPython 3.14, about 18 are byte transforms instead of character sets: , , , , , and similar. is the only entry point in the module that does not consult , so it accepts all of them. Sending wraps the request stream in a bz2 decompressor before reads it. The ordering is what makes this exploitable. Django charges against the bytes that arrived on the wire: hands an , and is where runs. Decompression happens afterwards, inside the parser, where nothing is counting. This is DRF's defect and not Django's. Django resolves the charset parameter and assigns , and does resolve byte transforms, but every Django consumer of goes through the text-codec API and fails closed. Both and raise . DRF is the only caller that hands the request stream to . ( ) and ( ) take the same client-named encoding but fail closed instead of amplifying. The sink was introduced by (PR #5147, 2017-05-24, "Improve memory footprint when reading large JSON requests"), first released in 3.6.4. The final comment on that PR observes the intended memory gain does not hold because decodes the whole stream, which is the same property that makes this expansion unbounded. No check has been added since. A one-line fix at : ### PoC Save as and run it. It builds its own payloads, runs each arm in a fresh subprocess (peak RSS is a high-water mark, so measuring several arms in one process reports near-zero growt

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • PyPI djangorestframework3.6.4 → 3.18.2
  • package pipversion unspecified
  • pip djangorestframework>= 3.6.4, < 3.18.2
  • pypi djangorestframeworkversion unspecified

How to fix CVE-2026-114136

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-114136. EPSS is 0.50%. Act only if a listed version of Django REST framework is is installed.

Which versions are affected?

Compare what you have installed with 3.6.4 → 3.18.2, >= 3.6.4, < 3.18.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-409; CWE-770: Allocation of Resources Without Limits or Throttling. EPSS 0.50%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Django security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 21, 2026 · NIST NVD

    Detected

    Django REST framework is a toolkit for building Web APIs. From 3.6.4 until 3.18.2, JSONParser.parse in rest_framework/parsers.py uses the client-supplied Content-Type charset value with codecs.getreader, which accepts byte-transform codecs such as bz2_codec rather than only text encodings. A remote unauthenticated client can therefore cause a compressed JSON request body to be expanded after Djang

  2. Oct 22, 2026 · GitHub Advisory Database

    Updated

    ### Summary An unauthenticated attacker can defeat Django's limit and force a worker process to allocate arbitrary memory, by naming a compression codec in the Content-Type charset parameter. A 108-byte request body produces a 50,331,648-character value inside the view, an amplification factor of 466,033, and grows process peak RSS by about 97 MiB. No application configuration is required beyond D

  3. Oct 22, 2026 · PyPA Advisory Database

    Fix available

    djangorestframework fixed in 3.18.2

  4. Oct 22, 2026 · PyPA Advisory Database

    Fix available

    djangorestframework fixed in 3.18.2

  5. Oct 22, 2026 · PyPA Advisory Database

    Updated

    ### Summary An unauthenticated attacker can defeat Django's limit and force a worker process to allocate arbitrary memory, by naming a compression codec in the Content-Type charset parameter. A 108-byte request body produces a 50,331,648-character value inside the view, an amplification factor of 466,033, and grows process peak RSS by about 97 MiB. No application configuration is required beyond D

Sources

  • CVE.orgVulnerability recordCVE-2026-114136

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-114136

    30-day exploitation probability 0.50%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-3547-9m27-7rxg

    Django REST framework: JSONParser applies an attacker-named codec to the request stream

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-114136

    An unauthenticated attacker can defeat Django's DATA_UPLOAD_MAX_MEMORY_SIZE limit and force a worker process to allocate arbitrary memory, by naming a compression codec in the Content-Type charset parameter. A 108-byte request body produces a 50,331,648-character value inside the view, an amplification factor of 466,033, and grows process peak RSS by about 97 MiB. No application configuration is r

    advisories.gitlab.com
  • NIST NVDVulnerability recordCVE-2026-114136

    Django REST framework is a toolkit for building Web APIs. From 3.6.4 until 3.18.2, JSONParser.parse in rest_framework/parsers.py uses the client-supplied Content-Type charset value with codecs.getreader, which accepts byte-transform codecs such as bz2_codec rather than only text

    nvd.nist.gov
  • PyPA Advisory DatabasePackage advisoryGHSA-3547-9m27-7rxg

    Django REST framework: JSONParser applies an attacker-named codec to the request stream

    osv.dev
  • Snyk Vulnerability DatabasePackage advisorySNYK-PYTHON-DJANGORESTFRAMEWORK-21431456

    Allocation of Resources Without Limits or Throttling

    security.snyk.io

References

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 2, 2026
  • Snyk Vulnerability DatabaseOct 24, 2026
  • GitHub Advisory DatabaseOct 23, 2026
  • GitLab Advisory DatabaseOct 23, 2026
  • PyPA Advisory DatabaseOct 23, 2026
  • CVE.orgOct 22, 2026
  • NIST NVDOct 22, 2026