
PEACH
Un cadre d’isolation des locataires
CVE-2026-115472 is an improper authorization vulnerability in Doorkeeper, an OAuth 2 provider for Ruby on Rails and Grape applications. The flaw exists in the OAuth token revocation flow, where public (non-confidential) clients are not correctly authorized before their revocation requests are processed, allowing any valid public client to revoke tokens belonging to other public clients. All Doorkeeper versions prior to 5.9.1 are affected. The vulnerability was published on November 17, 2026, and carries a CVSS v3.1 base score of 6.5 (Medium) (GitHub Advisory, Feedly).
The root cause is classified as CWE-285 (Improper Authorization). In app/controllers/doorkeeper/tokens_controller.rb, the authorized? method contained the condition token.application_id? && token.application.confidential?, which only enforced token ownership checks for confidential clients. Because public clients are not confidential, this condition evaluated to false, causing the code to fall through to an else branch that unconditionally returned true — meaning any authenticated public client could revoke tokens issued to any other public client, violating RFC 7009 Section 5. The fix removes the confidential? guard so that all tokens with an application_id require the requesting client's ID to match the token's application ID (GitHub PR #1808, Fix Commit).
Successful exploitation allows an unauthenticated or minimally authenticated attacker (possessing only a valid public client_id) to revoke OAuth access tokens or refresh tokens belonging to other users or applications using public clients. This can result in forced session termination, denial of service for legitimate users, and potential account lockout scenarios. Confidentiality and integrity are both assessed as low-impact, with no direct availability impact at the infrastructure level, though user-facing service disruption is a realistic consequence (GitHub Advisory, Feedly).
No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the disclosure date. The EPSS score is 0.0, indicating very low current exploitation probability, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The attack requires no privileges and no user interaction, and is network-accessible, making it relatively straightforward to attempt against any application using Doorkeeper with public OAuth clients (Feedly, GitHub Advisory).
client_id on the target application — public clients do not require a client_secret./oauth/revoke endpoint with the attacker's client_id and the victim's token value:POST /oauth/revoke
Content-Type: application/x-www-form-urlencoded
client_id=<attacker_public_client_id>&token=<victim_token>/oauth/revoke from unexpected IP addresses or clients, particularly where the client_id in the request does not match the application that originally issued the token.unauthorized_client errors on the revocation endpoint alongside successful revocations from mismatched client IDs; patterns of multiple tokens being revoked in rapid succession from a single client_id.Upgrade Doorkeeper to version 5.9.1 or later, which removes the confidential? guard from the authorized? method so that all tokens with an application_id require client ownership verification before revocation (GitHub Release v5.9.1). No configuration-based workaround is available for versions prior to 5.9.1; upgrading is the only remediation. Applications that use only confidential OAuth clients are not affected by this specific bypass, but upgrading is still strongly recommended.
The vulnerability was reported by researcher ThisIsMissEm and the fix was contributed by community members 55728 (with a reproduction test from mainameiz), reflecting active community engagement in Doorkeeper's security. The GitHub advisory was published with full details withheld until 2026-08-28 to allow time for users to upgrade. No significant broader media coverage or notable public commentary beyond the GitHub repository has been identified (GitHub Advisory, GitHub PR #1808).
Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.
Source: Ce rapport a été généré à l’aide de l’IA
Évaluation gratuite des vulnérabilités
Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.
Obtenez une démo personnalisée
"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."