CVE-2026-43001
Openstack Keystone broken access control
- Published1 May 2026
Description
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 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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:LAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:39808
- https://access.redhat.com/errata/RHSA-2026:54757
- https://access.redhat.com/security/cve/CVE-2026-43001
- https://bugs.launchpad.net/keystone/+bug/2149775
- https://bugzilla.redhat.com/show_bug.cgi?id=2464305
- https://review.opendev.org/c/openstack/keystone/+/985804
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43001.json
- https://security.openstack.org/ossa/OSSA-2026-015.html
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-43001 being actively exploited?
CVE-2026-43001 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.59%.
How severe is CVE-2026-43001?
CVE-2026-43001 has a CVSS 3.1 base score of 7.9, rated high. EPSS estimates a 0.59% probability of exploitation.
Which products are affected by CVE-2026-43001?
Affected products include Openstack Keystone.
How do I fix CVE-2026-43001?
Upgrade affected software to a fixed version, for example Openstack Keystone 27.0.2 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-43001 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.