CVE-2026-22797: An issue was discovered in OpenStack keystonemiddleware 10.5 through 10.7 before 10.7.2, 10.8 and 10.9 befo...
An issue was discovered in OpenStack keystonemiddleware 10.5 through 10.7 before 10.7.2, 10.8 and 10.9 before 10.9.1, and 10.10 through 10.12 before 10.12.1. The external_oauth2_token middleware fails to sanitize incoming authentication headers before processing OAuth 2.0 tokens. By sending forged identity headers such as X-Is-Admin-Project, X-Roles, or X-User-Id, an authenticated attacker may escalate privileges or impersonate other users. All deployments using the external_oauth2_token middleware are affected.
Security readout for executives and security teams
This flaw affects some OpenStack deployments using keystonemiddleware external OAuth 2.0 token handling. An authenticated user may supply forged identity headers that are incorrectly trusted, potentially becoming an admin or another user. Business impact is high where OpenStack APIs manage sensitive infrastructure. Exposure is limited to OpenStack deployments running affected keystonemiddleware versions and using the external_oauth2_token middleware. Network-reachable OpenStack APIs are higher priority because exploitation requires only authenticated access, low complexity, and no user interaction. Treat as urgent for OpenStack environments using external OAuth 2.0 token middleware. The vulnerability can undermine cloud administrative boundaries, so remediation should be scheduled ahead of normal patch cycles for exposed or multi-tenant deployments. Mitigation focus: Upgrade keystonemiddleware to 10.7.2, 10.9.1, 10.12.1, or later as applicable.; Apply relevant Red Hat advisories where using Red Hat-packaged OpenStack components.; Identify and prioritize deployments using external_oauth2_token middleware..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
3ADP providers
11Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.