CVE-2026-44394

openstack-keystone: OpenStack Keystone: Federated token rescoping allows indefinite access

Published May 28, 2026 CVSS 3.1 · 6 Medium EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4611-1 keystone security update
Debian DSA Debian DSA DSA-6331-1 keystone security update
Github GHSA Github GHSA GHSA-whqr-fgm5-x77q OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token
Ubuntu USN Ubuntu USN USN-8433-1 OpenStack Keystone vulnerabilities
History
Type Values Removed Values Added
Title Keystone Federated Token Rescoping Causing Indefinite Token Lifetime openstack-keystone: OpenStack Keystone: Federated token rescoping allows indefinite access
Weaknesses CWE-613
References
Metrics threat_severity

None

threat_severity

Moderate

Type Values Removed Values Added
Title Keystone Federated Token Rescoping Causing Indefinite Token Lifetime
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

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

{'score': 6, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
May 28, 2026, 7:43 PM
Reserved
May 5, 2026, 12:00 AM
Status
Analyzed
Published
May 28, 2026, 7:16 PM
Modified
Oct 26, 2026, 1:10 PM
Severity
Moderate
Public date
May 28, 2026, 12:00 AM