Security readout for executives and security teams
Plain-English summary
CVE-2026-43001 lets a privileged holder of an unrestricted OpenStack Keystone application credential for one project obtain access scoped to another project. This is not a drive-by internet bug, but it can enable lateral movement inside a cloud if credential boundaries are trusted for tenant isolation.
Executive priority
Treat as high priority for multi-tenant OpenStack environments or clouds where Keystone project boundaries protect sensitive workloads. The business risk is cross-project access after credential compromise, not broad unauthenticated takeover.
Technical view
Keystone before 29.0.2 failed to ensure caller-supplied project_id for EC2-type credentials matched the authenticating application credential’s project. A later EC2 token exchange could issue a token scoped to the other project while retaining the original app_cred_id. The CVSS score is 8.0 with high privileges and high attack complexity.
Likely exposure
Exposure is most relevant to OpenStack Keystone deployments before 29.0.2 that use application credentials and EC2 credential/token compatibility flows. Organizations without Keystone, without application credentials, or without EC2 credential use appear less exposed based on the supplied sources.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires an attacker already holding an unrestricted application credential for one project, so the main risk is post-compromise lateral movement across projects within the credential owner’s role footprint.
Researcher notes
The core weakness is missing authorization consistency between an application credential’s project and the EC2 credential project_id. Evidence supports Keystone before 29.0.2, CVSS 8.0, CWE-1288 and CWE-863. Do not assume broader products or exploitation without vendor evidence.
Mitigation direction
- Upgrade OpenStack Keystone to 29.0.2 or later where applicable.
- Apply vendor fixed packages, including Red Hat advisories where they match your platform.
- Review OpenStack OSSA-2026-015 and Keystone bug guidance for deployment-specific actions.
- Rotate exposed or suspicious application credentials after patching.
- Restrict use of unrestricted application credentials where operationally feasible.
Validation and detection
- Inventory Keystone versions and identify deployments before 29.0.2.
- Check whether application credentials and EC2 credential/token flows are enabled.
- Review credential records for EC2 credentials scoped outside the application credential’s project.
- Review audit logs for unusual cross-project token issuance tied to app_cred_id values.
- Confirm vendor advisories apply to your distribution and package stream.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-1288: 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.
Open ATT&CK lookupCWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-43001 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H1.36redhat-SADPCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:L1.36mitreVulnerability scoring details
Base CVSS 3.1 score
8HighVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
Base CVSS 3.1 score
7.9HighVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-05-01T09:00:55.408Z: Reported to Red Hat.
- 2026-05-01T00:00:00.000Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://bugs.launchpad.net/keystone/+bug/2149775CVE reference, mitre
- https://review.opendev.org/c/openstack/keystone/+/985804CVE reference, mitre
- https://security.openstack.org/ossa/OSSA-2026-015.htmlCVE reference, mitre
- https://access.redhat.com/security/cve/CVE-2026-43001CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2464305CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43001.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:39808CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Validation of Consistency within Input
Improper Validation of Consistency within Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.