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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 5
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-23 15:08
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-22 17:34
- StatusReceived → PublishedNVD modified 2026-10-21 20:06
- StatusPublished → ReceivedNVD modified 2026-10-21 21:17
- First seenCVSS 7.4 · encodeNVD modified 2026-10-21 20:06
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.