CVE-2026-114137 Django REST framework: TokenProxy.delete() reports success and revokes nothing
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-114137?
CVE-2026-114137 is a high-severity vulnerability in encode django-rest-framework, published on 21 Oct 2026.
Official 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.
Which versions are affected by CVE-2026-114137?
2 open source packages ship an affected version, including djangorestframework.
| Package | Affected | Fixed in |
|---|---|---|
djangorestframework PyPI | From 3.12.0 | 3.18.2 |
djangorestframework PyPI | From 3.12.0 | 3.18.2 |
How do I fix CVE-2026-114137?
Upgrade djangorestframework to 3.18.2 or later.
Is CVE-2026-114137 being exploited?
There is no known exploitation of CVE-2026-114137 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2026-114137, ECHO-33bc-b8a5-ee1f, GHSA-xw6w-gcfp-cf8m, ROOT-APP-PYPI-CVE-2026-114137, UBUNTU-CVE-2026-114137.