CVE-2026-43001: OpenStack Keystone · Incorrect Authorization
Affects OpenStack KeystoneSource CVE Database V5
Not known to be exploited · CVSS 7.9 High · fixed in 29.0.2 : patch OpenStack Keystone soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 29.0.2, 28.0.2, 27.0.2
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade OpenStack Keystone to 29.0.2, 28.0.2 or 27.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenStackKeystone | Affected
| Fixed in
|
| OpenStackKeystone | Affected
| Fixed in
|
| OpenStackKeystone | Affected
| Fixed in
|
PyPIkeystonepkg:pypi/keystoneOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability. Vendors managing cloud-hosted OpenStack Keystone services typically apply fixes server-side. Administrators should ensure application credentials are scoped with the least privilege necessary. If EC2 credentials are not used, consider disabling the EC2 credential API endpoint in Keystone to prevent unauthorized cross-project credential creation. Refer to the OpenStack Keystone administration guide for detailed instructions. Applying the official vendor patches and configuration changes is recommended to fully remediate this issue.
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.
References
- bugs.launchpad.net/keystone/+bug/2149775 (opens in a new tab)
- review.opendev.org/c/openstack/keystone/+/985804 (opens in a new tab)
- security.openstack.org/ossa/OSSA-2026-015.html (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-43001 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2464305 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43001.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:39808 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:54757 (opens in a new tab)