Skip to content
fr Sign in
6.0 Medium

CVE-2026-44394 An issue was discovered in OpenStack Keystone before 29.0.2

Description

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.

Affected products and versions

Product Affected versions Fixed in
Keystone 29.0 29.0.0 → < 29.0.2 29.0.2
Keystone 28.0 28.0.0 → < 28.0.2 28.0.2
Keystone 14.0 14.0.0 → < 27.0.2 27.0.2

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Keystone

The 13 CVEs of Keystone →
CVE-2026-90460 An issue was discovered in OpenStack Keystone before 29.0.3 7.6 High CVE-2026-80183 In OpenStack Keystone before 29.0.3, any authenticated user holding role:reader on any project can list every… 7.1 High CVE-2026-80184 In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens,… 7.6 High CVE-2026-80182 In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped… 7.6 High
Track this CVE