Read the docs

TokenProxy.delete() in Django REST framework silently revokes nothing

Priority LOW 35CWE-390Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Partial Red Hat: 1 fixed, 2 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-613.

Summary

Django REST framework from 3.12.0 before 3.18.2 is affected. TokenProxy.delete() uses the user ID instead of the token key, so the deletion matches no row and reports zero deletions without raising an error. Applications or scripts that revoke tokens through a TokenProxy can believe revocation succeeded while the token keeps authenticating. DRF tokens do not expire automatically, so that access can continue indefinitely (CWE-390).

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00512 43rd percentileScored 2026-11-07
Fix Partial django-rest-framework (encode): 3.18.2djangorestframework (PyPI): 3.18.2Red Hat: 1 advisoryRed Hat: 1 fixed, 2 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
encodedjango-rest-framework3.12.0 to before 3.18.23.18.2Patch availableCNA
—djangorestframework (PyPI)3.12.0 to before 3.18.23.18.2Patch availableGHSA-xw6w-gcfp-cf8m
  • django-rest-framework Vendorencode Affected 3.12.0 to before 3.18.2 Fixed in 3.18.2 Patch available CNA
  • djangorestframework (PyPI) Vendor— Affected 3.12.0 to before 3.18.2 Fixed in 3.18.2 Patch available GHSA-xw6w-gcfp-cf8m

Remediation

Upgrade djangorestframework (PyPI) and django-rest-framework (encode) to 3.18.2. Red Hat fixes the flaw in Red Hat Discovery 2 through RHSA-2026:94802. Red Hat lists Red Hat Ansible Automation Platform 2 and Red Hat Satellite 6 as affected with no fix available.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

  • Fix · CNA django-rest-framework (encode) Fixed in 3.18.2
  • Fix · GHSA-xw6w-gcfp-cf8m djangorestframework (PyPI) Fixed in 3.18.2 Advisory →

Red Hat 1 advisory

  • RHSA-2026:94802 Released 2026-11-04 · Red Hat rating Critical
    A Subscription Management tool for finding and reporting Red Hat product usage
    • Red Hat Discovery 2 registry.redhat.io/discovery/discovery-server-rhel9, registry.redhat.io/discovery/discovery-ui-rhel9

Vendor assessments

Red Hat

Red Hat rating: Important. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Ansible Automation Platform 2AffectedNo fix yet
Red Hat Satellite 6AffectedNo fix yet
Red Hat Discovery 2Fixed RHSA-2026:94802
Not affected: 3 products
  • Red Hat Ansible Automation Platform 2
  • Red Hat Discovery 2
  • Red Hat Update Infrastructure 4 for Cloud Providers

Timeline

  1. 2026-10-21 Threatist record created from CVE-2026-114137
  2. 2026-10-22 Affected versions changed · Red Hat
  3. 2026-10-22 CVSS score added · Red Hat
  4. 2026-10-22 Alias added: GHSA-xw6w-gcfp-cf8m
  5. 2026-10-22 Fix available: PyPI/[email protected] · GHSA-xw6w-gcfp-cf8m
  6. 2026-10-22 CVSS score added · GHSA-xw6w-gcfp-cf8m
  7. 2026-10-22 Weakness changed · GHSA-xw6w-gcfp-cf8m
  8. 2026-10-22 5 new references · GHSA-xw6w-gcfp-cf8m
  9. 2026-10-23 Affected versions changed · Red Hat
  10. 2026-10-23 Priority changed: MEDIUM → LOW
  11. 2026-10-23 CISA SSVC decision points changed
  12. 2026-10-26 Affected versions changed · Red Hat
  13. 2026-11-04 Fix available: RHSA-2026:94802 · Red Hat
  14. 2026-11-04 Fix available: Red Hat Discovery 2 · Red Hat

References

  • TI-2026-35991 Starlette has missing Host header validation that poisons request.url.path, bypassing path-based security checks KEVCVSS 3.1MEDIUM 6.5
  • TI-2024-32128 Starlette Denial of service (DoS) via multipart/form-data CVSS 4.0HIGH 8.7
  • TI-2026-78981 Django REST framework Accept header parsing causes excessive CPU use CVSS 3.1HIGH 7.5
  • TI-2026-78978 Django REST framework JSONParser accepts attacker-chosen codecs CVSS 3.1HIGH 7.5
  • TI-2024-16279 python-multipart vulnerable to content-type header Regular expression Denial of Service CVSS 3.1HIGH 7.5
  • TI-2023-13590 Path traversal in encode Starlette CVSS 3.1HIGH 7.5
See all 18 →

Sources