Recommended action

Update keystone to 27.0.2; keystone to 28.0.2; keystone to 29.0.2 if you use the affected versions. Test the change in a non-production environment first.

hol-guard supply-chain scan

What this means

OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token affects keystone (pip), keystone (pip), keystone (pip). Severity is medium. 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.

AI coding agents often install or upgrade packages automatically in pip. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.

Affected software

Recommended action

Update keystone to 27.0.2; keystone to 28.0.2; keystone to 29.0.2 if you use the affected versions. Test the change in a non-production environment first.

hol-guard supply-chain scan

What this means

OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token affects keystone (pip), keystone (pip), keystone (pip). Severity is medium. 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.

AI coding agents often install or upgrade packages automatically in pip. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.

Affected software