How severe is CVE-2026-43001?

CVE-2026-43001 has a CVSS 3.x base score of 7.9, rated high severity. It is exploitable over network with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.

Is CVE-2026-43001 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (36th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-43001?

CVE-2026-43001 affects Openstack Keystone. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-43001?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-43001 have an EU (EUVD) identifier?

Yes. CVE-2026-43001 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26488.

When was CVE-2026-43001 published?

CVE-2026-43001 was published on 2026-05-01 and last updated on 2026-06-30.

CVE-2026-43001

CVE-2026-43001 is a high-severity vulnerability in Openstack Keystone with a CVSS 3.x base score of 7.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-863.

Key facts

Severity: High (CVSS 3.x base score 7.9)
EPSS exploit prediction: 0% (36th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-26488
Weakness: CWE-863
Affected product: Openstack Keystone
Published: 2026-05-01
Last modified: 2026-06-30

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.

Frequently asked questions

What is CVE-2026-43001?: 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.
How severe is CVE-2026-43001?: CVE-2026-43001 has a CVSS 3.x base score of 7.9, rated high severity. It is exploitable over network with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.
Is CVE-2026-43001 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (36th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-43001?: CVE-2026-43001 affects Openstack Keystone. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-43001?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-43001 have an EU (EUVD) identifier?: Yes. CVE-2026-43001 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26488.
When was CVE-2026-43001 published?: CVE-2026-43001 was published on 2026-05-01 and last updated on 2026-06-30.

References

Affected products (1)

cpe:2.3:a:openstack:keystone:*:*:*:*:*:*:*:*

More vulnerabilities in Openstack Keystone

CVE-2020-12691 — High (CVSS 8.8): An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any authenticated user can create an EC2…
CVE-2020-12690 — High (CVSS 8.8): An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The list of roles provided for an OAuth1…
CVE-2020-12689 — High (CVSS 8.8): An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any user authenticated within a limited scope…
CVE-2019-19687 — High (CVSS 8.8): OpenStack Keystone 15.0.0 and 16.0.0 is affected by Data Leakage in the list credentials API. Any user with a role on a…
CVE-2014-2828 — High (CVSS 7.8): The V3 API in OpenStack Identity (Keystone) 2013.1 before 2013.2.4 and icehouse before icehouse-rc2 allows remote…
CVE-2021-38155 — High (CVSS 7.5): OpenStack Keystone 10.x through 16.x before 16.0.2, 17.x before 17.0.1, 18.x before 18.0.1, and 19.x before 19.0.1…

All CVEs affecting Openstack Keystone →

Other CWE-863 (Incorrect Authorization) vulnerabilities

CVE-2026-48286 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) versions 7.4.3 build 9396 and earlier are affected by an Incorrect Authorization…
CVE-2026-48303 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) versions 7.4.3 build 9394 and earlier are affected by an Incorrect Authorization…
CVE-2026-44330 — Critical (CVSS 10.0): free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's NEF mounts the…
CVE-2026-46595 — Critical (CVSS 10.0): Previously, CVE-2024-45337 fixed an authorization bypass for misused ssh server configurations; if any other type of…
CVE-2026-33105 — Critical (CVSS 10.0): Improper authorization in Microsoft Azure Kubernetes Service allows an unauthorized attacker to elevate privileges over…
CVE-2026-32213 — Critical (CVSS 10.0): Improper authorization in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.

Browse all CWE-863 (Incorrect Authorization) vulnerabilities →