Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:LSummary
CVE-2026-43001 is a high-severity Incorrect Authorization (CWE-863) vulnerability in Openstack Keystone. Its CVSS base score is 7.9 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-25 (Reference Monitor) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-43001 is a vulnerability affecting OpenStack Keystone versions 13 through 29. The flaw occurs in the POST /v3/credentials endpoint, which does not validate that the caller-supplied project_id for an EC2-type credential matches the project associated with the authenticating application credential. This issue, published on 2026-05-01, is categorized under CWE-863 (Incorrect Authorization) and carries a CVSS v3.1 base score of 7.9 (AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:L).
An attacker with an unrestricted application credential scoped to project A can exploit this vulnerability over the network. By creating an EC2-type credential specifying a project_id for project B, the attacker can then perform a /v3/ec2tokens exchange to obtain a Keystone token scoped to project B. This token retains the original app_cred_id, enabling cross-project lateral movement within the footprint of the credential owner's roles, potentially granting high confidentiality and integrity impacts across scope boundaries.
Advisories and patches addressing this vulnerability are detailed in the OpenStack Keystone bug tracker at https://bugs.launchpad.net/keystone/+bug/2149775 and the associated code review patch at https://review.opendev.org/c/openstack/keystone/+/985804.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26488
Vulnerability Data
An issue was discovered in OpenStack Keystone before 29.0.2. POST /v3/credentials did not validate that the caller-supplied project_id for an EC2-type credential matched the project of the authenticating application credential. This allowed an attacker holding an unrestricted application credential for…
more
project A to create an EC2 credential targeting project B; a subsequent /v3/ec2tokens exchange would then issue a Keystone token scoped to project B while still carrying the original app_cred_id, enabling cross-project lateral movement within the credential owner's role footprint.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 3 OS baselines
V2.2.2V4.2.3V12.3.2
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly requires correct enforcement of authorization decisions on every access request, structurally preventing incorrect checks.
AC-24 ensures access-control decisions are made and applied consistently, reducing the chance of an incorrect authorization result.
A reference monitor that is always invoked and tamper-proof forces every authorization decision through a verified, correct path.
SI-10 requires validity checks on supplied inputs, directly stopping acceptance of internally inconsistent complex data.
Least-privilege assignments shrink the set of authorizations that must be checked correctly, limiting exposure to flawed checks.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect consistency flaws but does not prevent them at design time.
Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.
Enforcing policy-driven approval and role-change reviews stops incorrect or stale authorization decisions from remaining in effect after job changes or terminations.
Secure development lifecycle requires input validation and consistency checks that directly address CWE-1288.
Application security requirements include validation of complex inputs and cross-field consistency.
Secure architecture principles encourage robust input handling but do not specifically mandate consistency validation.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248581 OL 8 must require users to provide a password for privilege escalation. prevents CWE-863
- V-252656 The OL 8 operating system must not be configured to bypass password requirements for privilege escalation. prevents CWE-863
RHEL 7 (1 rule)
- V-204430 The Red Hat Enterprise Linux operating system must be configured so that users must re-authenticate for privilege escalation. prevents CWE-863
RHEL 8 (1 rule)
- V-251712 The RHEL 8 operating system must not be configured to bypass password requirements for privilege escalation. prevents CWE-863