Doorkeeper: When using public clients, any client can revoke any access tokenGHSA-h5m9-42h9-vcq6
MEDIUMFix: doorkeeper-gem/doorkeeper#1808GHSA-h5m9-42h9-vcq6 is a medium-severity (CVSS 6.5) CWE-285 vulnerability in doorkeeper. A fix is available for doorkeeper — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-h5m9-42h9-vcq6.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
doorkeeperReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape. Prior to 5.9.1, Doorkeeper's OAuth token revocation flow does not correctly authorize revocation requests when public, non-confidential clients are used, allowing tokens to be revoked without correct authorization. This issue is fixed in version 5.9.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | doorkeeper | all versions | 5.9.1bundle update doorkeeper --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for doorkeeper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update doorkeeper to 5.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5m9-42h9-vcq6 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-h5m9-42h9-vcq6 in your dependencies?
Find it across RubyGems, including transitive dependencies.