Description
A flaw was found in OpenStack Keystone where delegation boundary enforcement is incomplete across trust, application credential, and OAuth1 authorization endpoints. Tokens obtained via delegated authentication methods, such as OAuth1 access tokens or custom Keystone authentication plugins, can perform operations beyond their intended scope because endpoint guards only recognized specific delegation types rather than using a comprehensive allowlist. This allows creating trusts that delegate roles beyond the token's authorized scope, creating persistent application credentials, and authorizing new OAuth1 delegations. These derived credentials persist independently and survive revocation of the original credential, enabling an attacker with a compromised narrow-scope credential to escalate to the user's full privileges and maintain persistent access.
Published: n/a
Score: 8.1 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability lies in OpenStack Keystone’s incomplete enforcement of delegation boundaries across trust, application credential, and OAuth1 endpoints. Tokens received through delegated authentication methods—such as OAuth1 access tokens or custom Keystone plugins—can be used to create trusts, persistent application credentials, and new OAuth1 delegations that grant roles beyond the token’s intended scope. As a result, a user possessing a narrow‑scope token can elevate privileges to the full user level and maintain long‑term access even after the original token is revoked.

Affected Systems

Any OpenStack Keystone deployment that has not applied the vendor patch is potentially vulnerable, including all instances that rely on the default trust, application credential, or OAuth1 authorization endpoints. No specific version ranges are listed, meaning the issue applies generically to Keystone installations using these delegated authentication mechanisms.

Risk and Exploitability

The CVSS score of 8.1 indicates high severity. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, so the overall exploitation probability cannot be precisely quantified. An attacker must first authenticate to Keystone or already have a valid delegated token and then invoke one of the affected endpoints. When exploited, the flaw allows a narrow‑scope token holder to gain full user privileges and persistently maintain access, posing a significant risk in environments that use delegated token authentication.

Generated by OpenCVE AI on August 26, 2026 at 02:13 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Keystone patch or upgrade to a fixed release as soon as it is available.
  • Configure the trust, application credential, and OAuth1 endpoints to enforce a strict allowlist of delegation types, rejecting any that are not explicitly permitted.
  • Revoke all existing delegated tokens, trusts, and application credentials that are no longer required, and rotate credentials to eliminate excess privileges.
  • Monitor Keystone logs for anomalous delegation activity and enforce least‑privilege access controls on all services.

Generated by OpenCVE AI on August 26, 2026 at 02:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 26 Aug 2026 01:45:00 +0000

Type Values Removed Values Added
First Time appeared Openstack
Openstack keystone
Vendors & Products Openstack
Openstack keystone

Wed, 26 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Description A flaw was found in OpenStack Keystone where delegation boundary enforcement is incomplete across trust, application credential, and OAuth1 authorization endpoints. Tokens obtained via delegated authentication methods, such as OAuth1 access tokens or custom Keystone authentication plugins, can perform operations beyond their intended scope because endpoint guards only recognized specific delegation types rather than using a comprehensive allowlist. This allows creating trusts that delegate roles beyond the token's authorized scope, creating persistent application credentials, and authorizing new OAuth1 delegations. These derived credentials persist independently and survive revocation of the original credential, enabling an attacker with a compromised narrow-scope credential to escalate to the user's full privileges and maintain persistent access.
Title keystone: keystone: Delegated token scope restrictions not consistently enforced across trust, OAuth1, and application credential endpoints
Weaknesses CWE-863
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Important


Subscriptions

Openstack Keystone
cve-icon MITRE

No data.

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity : Important

Publid Date: 2026-08-25T15:00:00Z

Links: CVE-2026-2035364 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-26T02:15:16Z

Weaknesses