keystone
Affected
- introduced
14.0.0, fixed27.0.2(ecosystem)
Fixed versions
27.0.2
Fix
- Fixed version
27.0.2pip install --upgrade keystone==27.0.2
Advisory
Also known as: CVE-2026-44394, PYSEC-2026-603
OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token
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.
Medium Basis: The source's own band: MODERATE
14.0.0, fixed 27.0.2 (ecosystem)27.0.2
27.0.2pip install --upgrade keystone==27.0.228.0.0, fixed 28.0.2 (ecosystem)28.0.2
28.0.2pip install --upgrade keystone==28.0.229.0.0, fixed 29.0.2 (ecosystem)29.0.2
29.0.2pip install --upgrade keystone==29.0.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0