NVD published 21 Oct 2026
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.
Signals
- KEV, exploited in the wild
- no
- EPSS, 30-day forecast
- 0.5%, 44th percentile (as of 18 Nov 2026)
- CVSS, NVD, HIGH
- 7.4
- Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Internet exposure
- not stated
Not in CISA's catalogue as of the last daily pull. Absence is not proof of safety.
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 1 dispatch
Public exploit code none in our sources
No public exploit in the sources we track: GitHub proof-of-concept lists, Metasploit and Exploit-DB. Absence is not proof that none exists.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.