Intel

AIKIDO-2026-595963

doorkeeper is vulnerable to Improper Authorization

Improper AuthorizationGHSA-h5m9-42h9-vcq6 Published Today

65

Medium Risk

This Affects:

RUBYdoorkeeper
0.0.1 - 5.9.0
Fixed in 5.9.1
Are you affected? Scan for Free

TL;DR

Doorkeeper's OAuth token revocation endpoint does not properly authorize revocation requests from public, non-confidential clients. A public client can submit a revocation request that revokes an access or refresh token it does not own. This breaks token isolation between public clients and can disrupt other clients' active sessions. The fix enforces proper client authorization on the revocation flow per RFC 7009 so a public client can only revoke its own tokens.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and your Doorkeeper provider issues tokens to public (non-confidential) clients.

Background info

doorkeeper is vulnerable to Improper Authorization in versions 0.0.1 - 5.9.0.

How to fix this

Upgrade the doorkeeper library to the patch version.