What’s Vulnerable › Vulnerabilities

CVE-2026-114137: Django REST framework: TokenProxy.delete() reports success and revokes nothing

• Severity: high (CVSS 7.4 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.5% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-10-21 · updated 2026-10-23
• Weakness: CWE-390

Description

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.

Affected products

• encode django-rest-framework: from 3.12.0, < 3.18.2

References

• https://github.com/encode/django-rest-framework/commit/af3fabfd517307fbc5d500fba1ab8f6e25f220b0
• https://github.com/encode/django-rest-framework/releases/tag/3.18.2
• https://github.com/encode/django-rest-framework/security/advisories/GHSA-xw6w-gcfp-cf8m

Get alerted when CVE-2026-114137 or the next vulnerability affects your stack