CVE-2026-114137 · GHSA-xw6w-gcfp-cf8m
Django REST framework: TokenProxy.delete() reports success and revokes nothing
- Risk score
- 60/100
- CVSS
- 7.4 v3.1
- Exploit chance (30 days)
- 0.4%
- Published
- 21 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- Django REST framework is a toolkit for building Web APIs. From 3.12.0 until 3.18.2, TokenProxy.delete() in rest_framework/authtoken/models.py uses the proxy's user-id pk while the concrete Token token-string primary key identifies rows, so Django issues a deletion query that matches no row and reports zero deletions w…
- Affected
- djangorestframework (pip) >= 3.12.0, < 3.18.2
- Fix
- Upgrade djangorestframework to 3.18.2 or later.
- Exploitation
- No known exploitation
Story map
At a glance
djangorestframework: Amber, patch this week. 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/media…
The flaws
- CVE-2026-114137: Django REST framework: TokenProxy.delete() reports success and revokes nothing (CVSS 7.4 · EPSS 0%)
- CVE-2026-114138: Django REST framework: Accept header with many large quoted parameters burns ~19s of CPU per request in content negotiation (CVSS 7.5 · EPSS 0%)
- CVE-2026-114136: Django REST framework: JSONParser applies an attacker-named codec to the request stream (CVSS 7.5 · EPSS 0%)
The fix
Upgrade djangorestframework: 3.18.2 or later on your release line
Who is exposed: djangorestframework (pip) < 3.18.2
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-390 (CWE-390). 5 other warnings in 30 days
Why it is Yellow
- CVSS 7.4 high
- Remotely exploitable without logging in
- On your watchlist: PyPI
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| djangorestframework | pip | >= 3.12.0, < 3.18.2 | 3.18.2 |
References
- https://github.com/advisories/GHSA-xw6w-gcfp-cf8m
- https://github.com/encode/django-rest-framework/security/advisories/GHSA-xw6w-gcfp-cf8m
- https://nvd.nist.gov/vuln/detail/CVE-2026-114137
- https://github.com/encode/django-rest-framework/commit/af3fabfd517307fbc5d500fba1ab8f6e25f220b0
- https://github.com/encode/django-rest-framework/releases/tag/3.18.2
- https://github.com/advisories/GHSA-xw6w-gcfp-cf8m
Original description
Django REST framework is a toolkit for building Web APIs. From 3.12.0 until 3.18.2, TokenProxy.delete() in rest_framework/authtoken/models.py uses the proxy's user-id pk while the concrete Token token-string primary key identifies rows, so Django issues a deletion query that matches no row and reports zero deletions without raising an error. Applications, administrative integrations, or operational scripts that revoke credentials through a TokenProxy instance can therefore believe revocation succeeded while the token remains live and continues authenticating. DRF's own TokenAdmin.delete_model workaround is not affected, but other callers can leave access available indefinitely because DRF tokens do not expire automatically. This issue is fixed in version 3.18.2.
Last activity 21 Oct 2026. Patch Forecast updates every hour.