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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-43001US | high8.0OT elevated | — | ||
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 projec… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/CVE-2026-43001WEB
- https://bugs.launchpad.net/keystone/+bug/2149775FIX
- https://bugzilla.redhat.com/show_bug.cgi?id=2464305REPORT
- https://github.com/advisories/GHSA-hhq2-3832-xxcvADVISORY
- https://review.opendev.org/c/openstack/keystone/+/985804FIX
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43001.jsonWEB
- https://security.openstack.org/ossa/OSSA-2026-015.htmlFIX
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan