No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Thu, 28 May 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 28 May 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| First Time appeared |
Openstack
Openstack keystone |
|
| Weaknesses | CWE-863 | |
| CPEs | cpe:2.3:a:openstack:keystone:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Openstack
Openstack keystone |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2026-05-28T19:43:05.616Z
Reserved: 2026-05-05T00:00:00.000Z
Link: CVE-2026-44394
Updated: 2026-05-28T19:42:54.602Z
Status : Received
Published: 2026-05-28T19:16:38.223
Modified: 2026-05-28T19:16:38.223
Link: CVE-2026-44394
No data.
OpenCVE Enrichment
No data.