Django REST framework: TokenProxy.delete() reports success and revokes nothing
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-114137
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 11:44 UTC · Revision 1
Source evidence
Django REST framework: TokenProxy.delete() reports success and revokes nothing
core-osv · Original sourcePublished 21 Oct 2026, 20:06 UTC
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.
osv:CVE-2026-114137
Complete source record
{
"id": "90acb3875ec766a168d1c18db10de6b47f30128284438e578980f0308622e0d7",
"url": "https://osv.dev/vulnerability/CVE-2026-114137",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Django REST framework: TokenProxy.delete() reports success and revokes nothing",
"summary": "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.",
"evidence": "osv:CVE-2026-114137",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-114137",
"aliases": [
"CVE-2026-114137",
"GHSA-xw6w-gcfp-cf8m"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/encode/django-rest-framework",
"type": "GIT",
"events": [
{
"introduced": "6f7aad8ffa96226672eacb82ab003dcf01070ed3"
},
{
"fixed": "69694a17d0b6ac14b4ea4d77916b73c68dc5a3e8"
},
{
"fixed": "af3fabfd517307fbc5d500fba1ab8f6e25f220b0"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "3.12.0"
},
{
"fixed": "3.18.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "af3fabfd517307fbc5d500fba1ab8f6e25f220b0"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "69694a17d0b6ac14b4ea4d77916b73c68dc5a3e8"
}
],
"source": "REFERENCES_TAG",
"original_tag": "3.18.2"
}
]
}
}
],
"versions": [
"3.18.1",
"3.18.0",
"3.17.1",
"3.17.0",
"3.16.1",
"3.16.0",
"3.15.2",
"3.15.1",
"3.15.0",
"3.14.0",
"3.13.1",
"3.13.0",
"3.12.4",
"3.12.3",
"3.12.1",
"3.12.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-114137.json"
}
}
],
"modified": "2026-10-28T02:30:34.682547824Z",
"provider": "osv",
"references": [
"https://github.com/encode/django-rest-framework/releases/tag/3.18.2",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/114xxx/CVE-2026-114137.json",
"https://github.com/encode/django-rest-framework/security/advisories/GHSA-xw6w-gcfp-cf8m",
"https://nvd.nist.gov/vuln/detail/CVE-2026-114137",
"https://github.com/encode/django-rest-framework/commit/af3fabfd517307fbc5d500fba1ab8f6e25f220b0"
],
"provider_metadata": {
"cwe_ids": [
"CWE-390",
"CWE-613"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/114xxx/CVE-2026-114137.json"
}
},
"related_cves": [
{
"value": "CVE-2026-114137",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 502075,
"published_at": "2026-10-21T20:06:57.79+00:00"
}