Incorrect Authorization Affecting openstack-keystone-2025.1 package, versions <27.0.1_git20260618-r6


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.25% (16th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-OPENSTACKKEYSTONE20251-17816707
  • published4 Jul 2026
  • disclosed28 May 2026

Introduced: 28 May 2026

CVE-2026-44394  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

Upgrade Chainguard openstack-keystone-2025.1 to version 27.0.1_git20260618-r6 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openstack-keystone-2025.1 package and not the openstack-keystone-2025.1 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1