NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2026-44394: OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token

mediumCVSS 3.1 6.0GHSA-whqr-fgm5-x77q

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 handlescopedtoken() function in the mapped authentication plugin returns response data without an expiresat value.

Published May 28, 2026 · Updated Jul 2, 2026

Affected packages

keystone

Ecosystem
PyPI
Affected
>= 14.0.0, < 27.0.2
Fixed in
27.0.2
Check
pip show keystone

keystone

Ecosystem
PyPI
Affected
>= 28.0.0, < 28.0.2
Fixed in
28.0.2
Check
pip show keystone

keystone

Ecosystem
PyPI
Affected
>= 29.0.0, < 29.0.2
Fixed in
29.0.2
Check
pip show keystone

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More PyPI vulnerabilities

All PyPI entries