CVEvulnerability
CVE-2026-44394
8.1 HIGH
Official page ↗
- Status
- Analyzed
- Published
- 2026-05-28
- Last modified
- 2026-10-26
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 6.0 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
- CVSS 3.1 ([email protected])
- 8.1 HIGH — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Weaknesses
- CWE-863
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 configurations
• openstack keystone (>= 14.0.0 < 27.0.2)
• openstack keystone (>= 28.0.0 < 28.0.2)
• openstack keystone (>= 29.0.0 < 29.0.2)
Related
Weakness · CWE (1)
- CWE-863 Incorrect Authorization weakness
Referenced by CWE · observed example (1)
- CWE-1475 Incomplete Data/State Propagation weakness
References
- 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