NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
💎
💎 RubyGems
Not in CISA KEV
MEDIUM severity

CVE-2026-115472 — doorkeeper

MEDIUMFix: doorkeeper-gem/doorkeeper@ecc1599

CVE-2026-115472 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.

Doorkeeper: When using public clients, any client can revoke any access token

Also known asGHSA-h5m9-42h9-vcq6
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2026-115472.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

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

1 pkg affected
💎doorkeeper

Real-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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemsdoorkeeperall versions5.9.1bundle update doorkeeper --conservative

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. Fix

    Update doorkeeper to 5.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-115472 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-115472 in your dependencies?

Find it across RubyGems, including transitive dependencies.

CVE-2026-115472: doorkeeper — Fixed in 5.9.1