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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
OpenStack Keystone
Default version status: unaffected
14.0.0 to < 27.0.2affected28.0.0 to < 28.0.2affected29.0.0 to < 29.0.2affected
References
- https://bugs.launchpad.net/keystone/+bug/2149775 ↗
- https://review.opendev.org/c/openstack/keystone/+/985804 ↗
- https://security.openstack.org/ossa/OSSA-2026-015.html ↗
- https://access.redhat.com/security/cve/CVE-2026-43001 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2464305 ↗
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43001.json ↗
- https://access.redhat.com/errata/RHSA-2026:54757 ↗
- https://access.redhat.com/errata/RHSA-2026:39808 ↗