Details
The control is what makes the trigger meaningful: it proves the row was deletable and the credential
check live, so the 200 after the proxy delete is a failed revocation and not a broken harness.
Reproduced identically on Django 6.1 and 5.2.17 LTS, so this is not a recent Django regression.
Impact
Failed credential revocation. An operator who revokes a token through a TokenProxy instance, and
receives no error, leaves a live credential in circulation indefinitely, because DRF auth tokens do
not expire on their own. Whoever holds that token benefits: a departed employee, a rotated
integration, a device believed to be deprovisioned, or an attacker whose access was thought to have
been cut during incident response.
No untrusted input reaches this code path, which is why the vector is scored AC:H. Exploitation
depends on the deployment revoking through the proxy, which is a natural thing to do givenTokenProxy is the model registered in the admin and the one most code will reach for. Any
deployment on 3.12.0 or later that revokes tokens outside DRF's own TokenAdmin.delete_model should
audit whether its revocations took effect.