CVE-2026-44394
An issue was discovered in OpenStack Keystone before 29.0.2. The …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- bugs.launchpad.net/keystone/+bug/2150379
- security.openstack.org/ossa/OSSA-2026-015.html
- nvd.nist.gov/vuln/detail/CVE-2026-44394
- github.com/pypa/advisory-database/tree/main/vulns/keystone/PYSEC-2026-603.yaml
- github.com/advisories/GHSA-whqr-fgm5-x77q
- nvd.nist.gov/vuln/detail/CVE-2026-44394
- cve.org/CVERecord?id=CVE-2026-44394
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.