cve.bz

CVE-2026-43001 openstack keystone: Incorrect Authorization

8.0 highExploit referenceEPSS 0.5%Fix available

High (8.0) in openstack keystone. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in keystone 27.0.2, 28.0.2, 29.0.2.

On this page
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.

Severity

CVSS 3.1

8.0 high
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-863 Incorrect Authorization
CWE-1288 Improper Validation of Consistency within Input
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-43001 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-43001?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-43001?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-43001 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-43001

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-43001](https://cve.bz/cve/badge/CVE-2026-43001.svg)](https://cve.bz/cve/CVE-2026-43001)

HTML:

<a href="https://cve.bz/cve/CVE-2026-43001"><img src="https://cve.bz/cve/badge/CVE-2026-43001.svg" alt="CVE-2026-43001"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenStack Keystonefrom 14.0.0 before 27.0.2
OpenStack Keystonefrom 28.0.0 before 28.0.2
OpenStack Keystonefrom 29.0.0 before 29.0.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hhq2-3832-xxcvPyPIkeystone>=13.0.0 <=29.0.1no fix published
PYSEC-2026-602PyPIkeystone>=14.0.0 <27.0.2
>=28.0.0 <28.0.2
>=29.0.0 <29.0.2
27.0.2, 28.0.2, 29.0.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12keystone2:22.0.2-0+deb12u3DEBIAN-CVE-2026-43001
Debian13keystone2:27.0.0-3+deb13u4DEBIAN-CVE-2026-43001
Debian14keystone2:29.0.1-2DEBIAN-CVE-2026-43001
Ubuntu22.04:LTSkeystone2:21.0.1-0ubuntu2.4UBUNTU-CVE-2026-43001
Ubuntu24.04:LTSkeystone2:25.0.0-0ubuntu1.4UBUNTU-CVE-2026-43001
Ubuntu25.10keystone2:28.0.0-0ubuntu1.3UBUNTU-CVE-2026-43001
Ubuntu26.04:LTSkeystone2:29.0.0-0ubuntu1.2UBUNTU-CVE-2026-43001
UbuntuPro:16.04:LTS, Pro:18.04:LTS, Pro:20.04:LTSkeystoneno fix listedUBUNTU-CVE-2026-43001
Red Hatopenstack:17.1::el9python3-keystone, openstack-keystone1:19.0.2-17.1.20260529190847.54dd95d.el9ostRHSA-2026:28044
Red Hatopenstack:17.1::el9python3-swift, openstack-swift, openstack-swift-proxy and 3 more0:2.27.1-17.1.20231004180819.el9ostRHSA-2026:28044
Red Hatopenstack:17.1::el9python3-tempest, openstack-tempest, openstack-tempest-all and 1 more1:33.0.0-17.1.20260406141650.1580f6f.el9ostRHSA-2026:28044
Red Hatopenstack:18.0::el9python3-keystone, openstack-keystone1:23.0.3-18.0.20260610133808.9e3dfb4.el9ostRHSA-2026:39808

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This flaw in OpenStack Keystone allows an attacker with an unrestricted application credential to bypass project isolation. By exploiting improper validation during EC2 credential creation, an attacker can gain unauthorized access and move laterally between projects within a Red Hat OpenStack Platform deployment, compromising multi-tenant security. If the roles from the original project the attacker holds a credential are compatible with the roles in the project the attacker is targeting, the attacker can perform the same actions granted permission from the initial project in the targeted project. Depending on the level of privileges the attacker has that means a high impact for confidentiality, availability and integrity.

Red Hat's mitigation

To reduce exposure, ensure that OpenStack application credentials are created with the most restrictive scope possible, limiting their permissions to only what is essential for their intended function. If EC2 credentials are not actively used within your OpenStack deployment, consider disabling the EC2 credential API endpoint in Keystone to prevent unauthorized creation of cross-project EC2 credentials. Refer to the OpenStack Keystone administration guide for detailed instructions on managing application credential scopes and disabling API endpoints. Any changes to Keystone configuration may require a service restart to take effect.

ProductPackageStateAdvisory
Red Hat OpenStack Platform 16.2openstack-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ostFixed 2026-08-13RHSA-2026:54757
Red Hat OpenStack Platform 16.2rhosp-rhel8/openstack-keystone:1:16.0.3-2.20260616134936.9d699a7.el8ostFixed 2026-08-13RHSA-2026:54757
Red Hat OpenStack Platform 17.1 for RHEL 9openstack-keystone-1:19.0.2-17.1.20260529190847.54dd95d.el9ostFixed 2026-06-22RHSA-2026:28044
Red Hat OpenStack Platform 17.1 for RHEL 9openstack-swift-0:2.27.1-17.1.20231004180819.el9ostFixed 2026-06-22RHSA-2026:28044
Red Hat OpenStack Platform 17.1 for RHEL 9openstack-tempest-1:33.0.0-17.1.20260406141650.1580f6f.el9ostFixed 2026-06-22RHSA-2026:28044
Red Hat OpenStack Platform 17.1 for RHEL 9rhosp-rhel9/openstack-keystone:1:19.0.2-17.1.20260529190847.54dd95d.el9ostFixed 2026-06-22RHSA-2026:28044
Red Hat OpenStack Services on OpenShift 18.0openstack-keystone-1:23.0.3-18.0.20260610133808.9e3dfb4.el9ostFixed 2026-07-15RHSA-2026:39808
Red Hat OpenStack Platform 13 (Queens)rhosp13/openstack-keystoneNot affected
Red Hat OpenStack Platform 18.0rhoso/openstack-keystone-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-43001.

References

Check your stackJSON