CVSS 3.1
8.0 highCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:HHigh (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.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:Hkeystone (PyPI): fixed in 27.0.2, 28.0.2, 29.0.2Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| OpenStack Keystone | from 14.0.0 before 27.0.2 |
| OpenStack Keystone | from 28.0.0 before 28.0.2 |
| OpenStack Keystone | from 29.0.0 before 29.0.2 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-hhq2-3832-xxcv | PyPI | keystone | >=13.0.0 <=29.0.1 | no fix published |
| PYSEC-2026-602 | PyPI | keystone | >=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 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | keystone | 2:22.0.2-0+deb12u3 | DEBIAN-CVE-2026-43001 |
| Debian | 13 | keystone | 2:27.0.0-3+deb13u4 | DEBIAN-CVE-2026-43001 |
| Debian | 14 | keystone | 2:29.0.1-2 | DEBIAN-CVE-2026-43001 |
| Ubuntu | 22.04:LTS | keystone | 2:21.0.1-0ubuntu2.4 | UBUNTU-CVE-2026-43001 |
| Ubuntu | 24.04:LTS | keystone | 2:25.0.0-0ubuntu1.4 | UBUNTU-CVE-2026-43001 |
| Ubuntu | 25.10 | keystone | 2:28.0.0-0ubuntu1.3 | UBUNTU-CVE-2026-43001 |
| Ubuntu | 26.04:LTS | keystone | 2:29.0.0-0ubuntu1.2 | UBUNTU-CVE-2026-43001 |
| Ubuntu | Pro:16.04:LTS, Pro:18.04:LTS, Pro:20.04:LTS | keystone | no fix listed | UBUNTU-CVE-2026-43001 |
| Red Hat | openstack:17.1::el9 | python3-keystone, openstack-keystone | 1:19.0.2-17.1.20260529190847.54dd95d.el9ost | RHSA-2026:28044 |
| Red Hat | openstack:17.1::el9 | python3-swift, openstack-swift, openstack-swift-proxy and 3 more | 0:2.27.1-17.1.20231004180819.el9ost | RHSA-2026:28044 |
| Red Hat | openstack:17.1::el9 | python3-tempest, openstack-tempest, openstack-tempest-all and 1 more | 1:33.0.0-17.1.20260406141650.1580f6f.el9ost | RHSA-2026:28044 |
| Red Hat | openstack:18.0::el9 | python3-keystone, openstack-keystone | 1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost | RHSA-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 rates this Important.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenStack Platform 16.2 | openstack-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost | Fixed 2026-08-13 | RHSA-2026:54757 |
| Red Hat OpenStack Platform 16.2 | rhosp-rhel8/openstack-keystone:1:16.0.3-2.20260616134936.9d699a7.el8ost | Fixed 2026-08-13 | RHSA-2026:54757 |
| Red Hat OpenStack Platform 17.1 for RHEL 9 | openstack-keystone-1:19.0.2-17.1.20260529190847.54dd95d.el9ost | Fixed 2026-06-22 | RHSA-2026:28044 |
| Red Hat OpenStack Platform 17.1 for RHEL 9 | openstack-swift-0:2.27.1-17.1.20231004180819.el9ost | Fixed 2026-06-22 | RHSA-2026:28044 |
| Red Hat OpenStack Platform 17.1 for RHEL 9 | openstack-tempest-1:33.0.0-17.1.20260406141650.1580f6f.el9ost | Fixed 2026-06-22 | RHSA-2026:28044 |
| Red Hat OpenStack Platform 17.1 for RHEL 9 | rhosp-rhel9/openstack-keystone:1:19.0.2-17.1.20260529190847.54dd95d.el9ost | Fixed 2026-06-22 | RHSA-2026:28044 |
| Red Hat OpenStack Services on OpenShift 18.0 | openstack-keystone-1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost | Fixed 2026-07-15 | RHSA-2026:39808 |
| Red Hat OpenStack Platform 13 (Queens) | rhosp13/openstack-keystone | Not affected | |
| Red Hat OpenStack Platform 18.0 | rhoso/openstack-keystone-rhel9 | Not 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.