Vulnerability in Encode Django-Rest-Framework
CVE-2026-114137
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.4 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Encode Django-Rest-Framework — versions >= 3.12.0, < 3.18.2
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-114137?
- CVE-2026-114137 is a high-severity vulnerability in Encode Django-Rest-Framework, classified under CWE-390. CVSS score: 7.4/10. Published 2026-10-21.
- How severe is CVE-2026-114137?
- High severity. CVSS v3 base score is 7.4 out of 10.