CVE-2026-80182: [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 OAuth1 access token, application credential, or trust-scoped authentication could create new long-lived credentials or authorize new delegations that persist independently of, and outlive, the credential used to obtain them. The delegation restrictions that block these operations did not consistently apply to all delegated token types, allowing an OAuth1-scoped token, for example, to create application credentials or authorize OAuth1 request tokens despite those operations being restricted for other delegated token types. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 29.0.3Patch OSSA-2026-037
Event History
Frequently Asked Questions
Which deployments are exposed?
All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected if running a version before 29.0.3. The provided data does not establish whether any of these mechanisms are enabled by default.
What does an attacker need to exploit this issue?
The attacker needs a token obtained through OAuth1 access-token authentication, an application credential, or trust-scoped authentication. Those delegated token types could bypass restrictions that should prevent certain credential-creation and delegation operations.
Why can the impact persist after the original delegated credential is no longer usable?
An attacker could create a new long-lived credential or authorize a new delegation that persists independently of the credential used to obtain it. As a result, invalidating or expiring only the original delegated credential may not remove access created through the flaw.