Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Django REST framework versions 3.12.0 up to 3.18.2 are affected. Calling delete() on a TokenProxy instance reports success but removes no database row, so the token keeps authenticating. An attacker needs no special access; the risk arises when operators or scripts revoke credentials through TokenProxy, which leaves tokens live. Upgrade to djangorestframework 3.18.2, which fixes the issue. Until then, revoke tokens through the concrete Token model or the admin delete path, and check that prior revocations took effect.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.4 | High | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0051, the 43rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:08 UTC First seen by agentprime
- 31 Oct 2026, 14:08 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-xw6w-gcfp-cf8m
- OSV: GHSA-xw6w-gcfp-cf8m
- github.com/encode/django-rest-framework/security/advisories/GHSA-xw6w-gcfp-cf8m
- nvd.nist.gov/vuln/detail/CVE-2026-114137
- github.com/encode/django-rest-framework/commit/af3fabfd517307fbc5d500fba1ab8f6e25f220b0
- github.com/encode/django-rest-framework
- github.com/encode/django-rest-framework/releases/tag/3.18.2