encode Django REST Framework up to 3.18.1 TokenProxy models.py TokenProxy.delete return value

Summaryinfo

A vulnerability was found in encode Django REST Framework up to 3.18.1. It has been classified as critical. This issue affects the function TokenProxy.delete of the file rest_framework/authtoken/models.py of the component TokenProxy. Performing a manipulation results in return value. This vulnerability is cataloged as CVE-2026-114137. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical has been found in encode Django REST Framework up to 3.18.1. This affects the function TokenProxy.delete of the file rest_framework/authtoken/models.py of the component TokenProxy. The manipulation with an unknown input leads to a return value vulnerability. CWE is classifying the issue as CWE-252. The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-114137 since 10/20/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.

Upgrading to version 3.18.2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Content Management System

Vendor

• encode

Name

• Django REST Framework

Version

• 3.18.0
• 3.18.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion