CVE-2026-80184: [OSSA-2026-037] OpenStack Keystone: Inconsistent scope enforcement for delegated tokens (CVE-2026-80182, CVE-2026-80184)
In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application credentials, trusts) could be submitted to the token-method authentication path for reauthentication to escape their intended project scope. When an application credential token was presented with no explicit scope, Keystone would issue a new token scoped to the credential owner's default project rather than the project for which the credential was issued, bypassing the intended project boundary. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.
Affected Software
Event History
Frequently Asked Questions
Which Keystone deployments need to be prioritized for remediation?
Deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected. Keystone versions before 29.0.3 require attention.
What access would an attacker need to exploit this issue?
An attacker needs low privileges and a delegated-authentication token obtained through an affected mechanism. The CVSS vector indicates network access, low attack complexity, no user interaction, and additional attack requirements.
What security impact can result from successful exploitation?
A delegated token can be reauthenticated in a way that escapes its intended project scope. In the application-credential case, an unscoped request can obtain a token for the credential owner's default project rather than the project originally assigned to the credential.