{"answers":{"affected":"2 open source packages ship an affected version, including djangorestframework.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114138 exists.","fix":"Upgrade djangorestframework to 3.18.2 or later.","what":"CVE-2026-114138 is a high-severity vulnerability in encode django-rest-framework, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114138 and fix it if it is affected.\n\nWhat it is: CVE-2026-114138 is a high-severity vulnerability in encode django-rest-framework, published on 21 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114138 exists.\n\nAffected packages and fixed versions:\n- djangorestframework (PyPI): affected all versions; fixed in 3.18.2\n- djangorestframework (PyPI): affected all versions; fixed in 3.18.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-114138/ (Markdown: https://insights.sbomify.com/CVE-2026-114138/index.md)","id":"CVE-2026-114138","markdown":"https://insights.sbomify.com/CVE-2026-114138/index.md","name":"CVE-2026-114138","record":{"aliases":["DEBIAN-CVE-2026-114138","ECHO-0cda-00c4-9b00","GHSA-33wh-fxxf-88vv","ROOT-APP-PYPI-CVE-2026-114138","UBUNTU-CVE-2026-114138"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Django REST framework is a toolkit for building Web APIs. Prior to 3.18.2, DefaultContentNegotiation.get_accept_list in rest_framework/negotiation.py accepts an unbounded number and aggregate size of Accept tokens, while select_renderer in that file repeatedly invokes _MediaType parsing from rest_framework/utils/mediatypes.py for each attacker-controlled token, every renderer, and forced 406 renegotiation. A remote unauthenticated client can send many distinct media types containing large quoted parameter values with numerous semicolons, causing Django's parameter parser and DRF's repeated parsing structure to consume disproportionate CPU. Requests to any reachable endpoint can pin synchronous workers for prolonged periods, and concurrent requests can make the service unavailable until the requests stop. This issue is fixed in version 3.18.2.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Django REST framework: Accept header with many large quoted parameters burns ~19s of CPU per request in content negotiation","id":"CVE-2026-114138","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Sentry-Javascript: Middleware Bypass when using Tunnel route","id":"CVE-2026-114139"},"packages":[{"ecosystem":"PyPI","fixed":["3.18.2"],"introduced":["0"],"last_affected":[],"package":"djangorestframework","purl":null,"source":"GHSA-33wh-fxxf-88vv"},{"ecosystem":"PyPI","fixed":["3.18.2"],"introduced":["0"],"last_affected":[],"package":"djangorestframework","purl":"pkg:pypi/djangorestframework","source":"GHSA-33wh-fxxf-88vv"}],"prev":{"headline":"Django REST framework: TokenProxy.delete() reports success and revokes nothing","id":"CVE-2026-114137"},"products":["django-rest-framework"],"published":"2026-10-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["encode"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114138/"}