# Django REST framework: TokenProxy.delete() reports success and revokes nothing

Advisory record · `GHSA-xw6w-gcfp-cf8m`

- **Identifiers:** `GHSA-xw6w-gcfp-cf8m` · `CVE-2026-114137`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-390](https://cwe.mitre.org/data/definitions/390.html) · [CWE-613](https://cwe.mitre.org/data/definitions/613.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-390](https://agentprime.io/advisories/tag/cwe-390.md)
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Oct 2026, 16:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `djangorestframework` (PyPI): affected `>=3.12.0, <3.18.2`; fixed in `3.18.2`

## 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.

Written 1 Nov 2026.

## 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

- 7.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`, from 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](https://osv.dev/vulnerability/GHSA-xw6w-gcfp-cf8m)

## Sources

- [GitHub Advisory Database: GHSA-xw6w-gcfp-cf8m](https://github.com/advisories/GHSA-xw6w-gcfp-cf8m)
- [OSV: GHSA-xw6w-gcfp-cf8m](https://osv.dev/vulnerability/GHSA-xw6w-gcfp-cf8m)
- <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>
- <https://github.com/encode/django-rest-framework>
- <https://github.com/encode/django-rest-framework/releases/tag/3.18.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xw6w-gcfp-cf8m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xw6w-gcfp-cf8m/>. Everything for agents: <https://agentprime.io/llms.txt>.