CVE-2026-44394

An issue was discovered in OpenStack Keystone before 29.0.2. The Keystone federated token rescoping mechanism does not propagate the original token's expiry to the newly issued token. When a federated user rescopes a token via POST /v3/auth/tokens, the handle_scoped_token() function in the mapped authentication plugin returns response data without an expires_at value. The token provider falls back to issuing a token with a fresh default TTL. By rescoping repeatedly before each token expires, a user can maintain access indefinitely, bypassing operator-configured token lifetime policies. This is a variant of CVE-2012-3426. Only deployments using federated identity (SAML2, OpenID Connect) are affected.
References
Link Resource
https://bugs.launchpad.net/keystone/+bug/2150379 Exploit Issue Tracking Patch Third Party Advisory
https://security.openstack.org/ossa/OSSA-2026-015.html Patch Vendor Advisory
Configurations

Configuration 1 (hide)

OR cpe:2.3:a:openstack:keystone:*:*:*:*:*:*:*:*
cpe:2.3:a:openstack:keystone:*:*:*:*:*:*:*:*
cpe:2.3:a:openstack:keystone:*:*:*:*:*:*:*:*

History

No history.

Information

Published : 2026-05-28 19:16

Updated : 2026-06-17 10:50


NVD link : CVE-2026-44394

Mitre link : CVE-2026-44394

CVE.ORG link : CVE-2026-44394


JSON object : View

Products Affected

openstack

  • keystone
CWE
CWE-863

Incorrect Authorization