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
openstack: keystone
References8
- security.openstack.org/ossa/OSSA-2026-015.html PatchVendor Advisory
- bugs.launchpad.net/keystone/+bug/2149775 ExploitIssue TrackingPatchThird Party Advisory
- review.opendev.org/c/openstack/keystone/+/985804 Patch
- access.redhat.com/errata/RHSA-2026:39808
- access.redhat.com/errata/RHSA-2026:54757
- access.redhat.com/security/cve/CVE-2026-43001
- bugzilla.redhat.com/show_bug.cgi?id=2464305
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43001…
Metrics
- CVSS 3.1
-
8.0
HIGH
Score source: NVD
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 41 · as of 13 November 2026
- CWE
- CWE-863CWE-1288
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.