CVE-2026-80184

keystone: keystone: Application credential tokens can escape project scope via token-method reauthentication

Published Aug 25, 2026 CVSS 4.0 · 7.6 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Tokens obtained through delegated authentication—OAuth1 access tokens, application credentials, and trusts—can be presented to Keystone’s token-method authentication endpoint to trigger reauthentication. When an application credential token is submitted without an explicit scope, Keystone mistakenly issues a new token scoped to the credential owner’s default project instead of the intended project, allowing an attacker to gain access beyond the intended boundaries.

Affected Systems

OpenStack Keystone versions earlier than 29.0.3 are affected whenever delegated authentication is enabled. Any deployment that permits OAuth1 access tokens, application credentials, or trusts without additional safeguards is vulnerable.

Risk and Exploitability

The CVSS score of 7.6 indicates a high severity. Although no EPSS score is available and the vulnerability is not listed in CISA KEV, the remote exploitability is clear: an attacker with valid delegated credentials can reauthenticate and obtain a token to the wrong project. The lack of a KEV listing suggests the vulnerability has not yet seen widespread exploitation, but the impact—loss of project isolation—underscores the need for timely remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Keystone release (29.0.3 or newer) to fix the scope handling flaw.
  • If an upgrade cannot be performed immediately, disable or restrict OAuth1, application credentials, and trust-based delegation until the patch is applied to prevent the unintended scoping of tokens.
  • Verify that token issuance now respects the requested scope by attempting reauthentication with an opaque token and confirming that the resulting project matches the original intent, then audit recent token logs for any unexpected project assignments.

Generated by OpenCVE AI on August 26, 2026 at 01:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4767-1 keystone security update
Debian DSA Debian DSA DSA-6480-1 keystone security update
History
Type Values Removed Values Added
References
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Escaped Project Scope via Delegated Authentication in Keystone keystone: keystone: Application credential tokens can escape project scope via token-method reauthentication
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N'}

threat_severity

Important

Type Values Removed Values Added
Title Escaped Project Scope via Delegated Authentication in Keystone
Type Values Removed Values Added
Description 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.
First Time appeared Openstack
Openstack keystone
Weaknesses CWE-863
CPEs cpe:2.3:a:openstack:keystone:*:*:*:*:*:*:*:*
Vendors & Products Openstack
Openstack keystone
References
Metrics cvssV4_0

{'score': 7.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Aug 26, 2026, 2:37 PM
Reserved
Aug 25, 2026, 9:29 PM
Status
Awaiting Analysis
Published
Aug 25, 2026, 10:17 PM
Modified
Sep 3, 2026, 6:11 PM
Severity
Important
Public date
Aug 25, 2026, 3:00 PM