Skip to content
Fencer Vulns
high 7.4

CVE-2026-114137 json

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

published 2026-10-21 18 d ago modified 2026-10-23 17 d ago also EUVD-2026-107547 , GHSA-xw6w-gcfp-cf8m

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi djangorestframework 3.18.2
  • encode django_rest_framework 3.18.2
  • django-rest-framework django_rest_framework 3.18.2
  • djangorestframework Debian 14 3.18.3+ds1-1

debian advisories DEBIAN-CVE-2026-114137

  • python-djangorestframework openSUSE Tumbleweed 3.18.2-1.1

opensuse advisories openSUSE-SU-2026:12277-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-114137 updated cvss 7.4

djangorestframework: djangorestframework: Unauthorized access via improper token revocation in TokenProxy

  • Red Hat Ansible Automation Platform 2 automation-controller 4.7.18-1.el9ap, ansible-automation-platform-26/hub-rhel9, ansible-automation-platform-27/hub-rhel9, python3.12-djangorestframework 3.15.1-2.el9ap, ansible-automation-platform-24/controller-rhel8, ansible-automation-platform-25/controller-rhel8, +6 more
    affected: no fix available, no fix planned “Will not fix”
  • Red Hat Satellite 6 python3-djangorestframework, satellite/iop-advisor-backend-rhel9, python-djangorestframework 3.14.0-1.el9ap, python3.12-djangorestframework 3.15.1-2.el9ap
    affected: no fix available
  • Red Hat Discovery 2 discovery/discovery-server-rhel9 1793734080
    fixed: vendor fix RHSA-2026:94802
  • Red Hat Ansible Automation Platform 2 python-djangorestframework 3.14.0-1.el9ap, python3x-djangorestframework 3.14.0-1.el8ap, ansible-automation-platform-26/gateway-rhel9, ansible-automation-platform-27/gateway-rhel9, python3.11-djangorestframework 3.15.1-1.el9ap, ansible-automation-platform-24/lightspeed-rhel8, +4 more Red Hat Discovery 2 discovery/discovery-ui-rhel9 1793733716 Red Hat Update Infrastructure 4 for Cloud Providers python-djangorestframework 3.14.0-1.el9ap
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
17 d ago

Exploit prediction

0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi djangorestframework
>=3.12.0, <3.18.2
3.18.2

Affected products

  • encode django-rest-framework

Classification

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

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.