An issue was discovered in OpenStack Keystone 13 through 29. POST /v3/credentials did not validate that the caller-supplied projectid 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 appcred_id, enabling cross-project lateral movement within the credential owner's role footprint.
{
"cwe_ids": [
"CWE-863"
],
"github_reviewed_at": "2026-05-07T02:39:59Z",
"github_reviewed": true,
"severity": "HIGH",
"nvd_published_at": "2026-05-01T09:16:17Z"
}