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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-390",
"CWE-613"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/114xxx/CVE-2026-114137.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "3.12.0"
},
{
"fixed": "3.18.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "af3fabfd517307fbc5d500fba1ab8f6e25f220b0"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "3.18.2",
"range": [
{
"fixed": "69694a17d0b6ac14b4ea4d77916b73c68dc5a3e8"
}
],
"source": "REFERENCES_TAG"
}
]
}