CVE Intelligence
High

CVE-2026-114137 — 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.

Published Oct 21, 2026 · Updated Oct 23, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.5% (30-day exploitation probability)+6
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.47%
ahead of 41% of scored CVEs · Oct 27, 2026
Affects
Encode
Django-rest-framework and 1 more
CVSS base
7.4
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Pip Djangorestframework: fixed in version 3.18.2 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Encode Django-rest-framework, Pip Djangorestframework).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Encode Django-rest-framework version >= 3.12.0, < 3.18.2 Vulnerable CVE Program (cve.org) e CISA ADP
Pip Djangorestframework ≥ 3.12.0 and < 3.18.2 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.4 CVSS 3.1 High 2.2 5.2 security-advisories@github.com via NIST National Vulnerability Database
7.4 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.4 CVSS 3.1 High — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-390

Other CVEs with this weakness →

EPSS over time FIRST

Oct 22, 2026 → Oct 27, 2026 · 6 reading(s) · max 0.47%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 23, 2026 · GitHub Security Advisories
  • Affected products added · pip/djangorestframework
    Oct 23, 2026 · GitHub Security Advisories
  • SSVC assessment updated
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Received → Awaiting Analysis
    Oct 22, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Received
    Oct 21, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 21, 2026
  • Affected products added · encode/django-rest-framework
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 7.4
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 21, 2026 · Alertas do Telegram
  • CVE published
    Oct 21, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 21, 2026 – Oct 23, 2026
  • 1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

5 on the record

Elsewhere on this site

Encode
every CVE for this vendor
CWE-390
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-114138 Django REST framework: Accept header with many large quoted parameters burns ~19s of CPU per request in content negotiation 6d
  • CVE-2026-114136 Django REST framework: JSONParser applies an attacker-named codec to the request stream 6d
  • CVE-2026-73229 Django REST framework: AdminRenderer may disclose GET-protected data when rendering invalid write requests Aug 11, 2026
  • CVE-2026-73228 Django REST framework: Potential bypass of Django `DATA_UPLOAD_MAX_MEMORY_SIZE` when parsing oversized JSON and urlencoded request bodies via DRF `request.data` Aug 11, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-114137 is "Django REST framework: TokenProxy.delete() reports success and revokes nothing", rated High. It affects Django-rest-framework (Encode); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.4 describes technical severity. EPSS 0.47% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.