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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://bugs.launchpad.net/keystone/+bug/2149775 Exploit, Issue Tracking, Patch, Third Party Advisory
- https://review.opendev.org/c/openstack/keystone/+/985804 Patch
- https://security.openstack.org/ossa/OSSA-2026-015.html Patch, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.0 · openstackNVD modified 2026-10-26 21:10
Affected (CPE criteria) 1
cpe:2.3:a:openstack:keystone:*:*:*:*:*:*:*:*
References 8
- https://bugs.launchpad.net/keystone/+bug/2149775 Exploit, Issue Tracking, Patch, Third Party Advisory
- https://review.opendev.org/c/openstack/keystone/+/985804 Patch
- https://security.openstack.org/ossa/OSSA-2026-015.html Patch, Vendor Advisory
- https://access.redhat.com/errata/RHSA-2026:39808
- https://access.redhat.com/errata/RHSA-2026:54757
- 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