CVE-2026-90460
Description
A flaw was found in OpenStack Keystone. Tokens obtained via delegated authentication methods (trusts, application credentials, OAuth1 access tokens) can move a credential to an unauthorized project by supplying a new project_id in a PATCH /v3/credentials request, because only the pre-update project is validated against the token's scope. Additionally, tokens obtained by authenticating with a non-delegated EC2 credential bypass the delegation scope restriction entirely and can access all credentials belonging to the same user, including TOTP multi-factor authentication seeds. Successful exploitation allows an attacker to exfiltrate sensitive authentication material or corrupt the project ownership of credentials.
Statement
Red Hat product impact analysis pending. Component mapping required to determine which products ship the affected code. OpenStack Keystone is shipped as part of Red Hat OpenStack Platform (RHOSP). Deployments using delegated authentication (trusts, application credentials, OAuth1) or EC2 credentials in combination with TOTP multi-factor authentication are most at risk. The insecure cross-project access config option allow_insecure_admin_trust_cross_project_credentials_access (default False) does not mitigate either of the two remaining vulnerabilities described here.
Mitigation
Where S3-compatible or other EC2-style authentication is not required, disable EC2 credentials and token exchange in Keystone: deny identity:ec2tokens_validate, identity:s3tokens_validate, and the OS-EC2 credential API rules in policy.yaml, or block POST /v3/ec2tokens and POST /v3/s3tokens in front of the Keystone API.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.1 | N/A | N/A |
| Attack Vector | Network | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | High | N/A | N/A |
| Integrity Impact | Low | N/A | N/A |
| Availability Impact | None | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Red Hat CVSS v3 Score Explanation
Independent verification (static): C:H for TOTP seed exposure via non-delegated EC2 token bypass; I:L for PATCH project_id move (reporter I:H overstated). See docs/SDLC/VM/openstack-keystone/CVE-2026-90460/verification-report.md.
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data; Read Files or Directories
An attacker could read sensitive data, either by reading the data directly from a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
Integrity
Technical Impact: Modify Application Data; Modify Files or Directories
An attacker could modify sensitive data, either by writing the data directly to a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access Control
Technical Impact: Gain Privileges or Assume Identity; Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
An attacker could gain unauthorized access to resources on the system and excessively consume those resources, leading to a denial of service.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
