OpenStack Keystone
In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application credentials, trusts) could be submitted to the token-method authentication path for reauthentication to escape their intended project scope. When an application credential token was presented with no explicit scope, Keystone would issue a new token scoped to the credential owner's default project rather than the project for which the credential was issued, bypassing the intended project boundary. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 13.0.0, < 27.0.3
- >= 28.0.0, < 28.0.3
- >= 29.0.0, < 29.0.3
Fixed in 27.0.3, 28.0.3, 29.0.3
Mitigation
Upgrade Keystone to 27.0.3 or 28.0.3 or 29.0.3 or later.
References
- Vendor advisory security.openstack.org/ossa/OSSA-2026-037.html
- Vendor advisory openwall.com/lists/oss-security/2026/08/25/5
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| CVE record (tagged exploit) | https://bugs.launchpad.net/keystone/+bug/2158538 | unknown | 14 Nov 2026 |