6
/ 10
MEDIUM
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
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.
Basic Information
ID
CVE-2026-44394
Source
mitre
Published
May 28, 2026 at 00:00
Modified
May 28, 2026 at 18:36
Affected Product
Vendor
OpenStack
Product
Keystone
Version
14.0.0
Affected Versions
OpenStack Keystone 14.0.0
OpenStack Keystone 28.0.0
OpenStack Keystone 29.0.0
OpenStack Keystone 28.0.0
OpenStack Keystone 29.0.0