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


- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114137, ECHO-33bc-b8a5-ee1f, GHSA-xw6w-gcfp-cf8m, ROOT-APP-PYPI-CVE-2026-114137, UBUNTU-CVE-2026-114137

## What is CVE-2026-114137?

CVE-2026-114137 is a high-severity vulnerability in encode django-rest-framework, published on 21 Oct 2026. 

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

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration), CWE-390 (Detection of Error Condition Without Action)

## Which versions are affected by CVE-2026-114137?

2 open source packages ship an affected version, including djangorestframework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `djangorestframework` | PyPI | From 3.12.0 | 3.18.2 |
| `djangorestframework` | PyPI | From 3.12.0 | 3.18.2 |

## How do I fix CVE-2026-114137?

Upgrade djangorestframework to 3.18.2 or later.

## Is CVE-2026-114137 being exploited?

There is no known exploitation of CVE-2026-114137 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114137 and fix it if it is affected.

What it is: CVE-2026-114137 is a high-severity vulnerability in encode django-rest-framework, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114137 in the wild and no public exploit code.

Affected packages and fixed versions:
- djangorestframework (PyPI): affected from 3.12.0; fixed in 3.18.2
- djangorestframework (PyPI): affected from 3.12.0; fixed in 3.18.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114137/ (Markdown: https://insights.sbomify.com/CVE-2026-114137/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114137
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114137
- OSV: https://osv.dev/vulnerability/CVE-2026-114137

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114137/
Summaries are generated and may contain mistakes; the official description above is the record.