Answer in brief
CVE-2026-44394 records a Medium severity (CVSS 6.0) vulnerability in OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token. The current sources do not mark it as known exploited. The current feed maps keystone (pip), keystone (pip), keystone (pip), keystone (pypi) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps keystone (pip), keystone (pip), keystone (pip), keystone (pypi) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| keystonepip | >=14.0.0,<27.0.2 | 27.0.2 |
| keystonepip | >=28.0.0,<28.0.2 | 28.0.2 |
| keystonepip | >=29.0.0,<29.0.2 | 29.0.2 |
| keystonepypi | >=14.0.0 <27.0.2 | 27.0.2 |
| keystonepypi | >=28.0.0 <28.0.2 | 28.0.2 |
| keystonepypi | >=29.0.0 <29.0.2 | 29.0.2 |
Published upstream
May 28, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Jul 2, 2026
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.
Quoted source text, attributed separately from HOL analysis.