CVE-2026-44394: [OSSA-2026-015] OpenStack Keystone: Multiple cdential delegation and authorization bypass vulnerabilities (CVE-2026-42998, CVE-2026-42999, CVE-2026-43000, CVE-2026-43001, CVE-2026-44394)

Published May 28, 2026
·
Updated

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. 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.

Affected Software

5 affected componentsFixes available
Openstack Keystone<29.0.2
Openstack Keystone>=14.0.0<27.0.2
Openstack Keystone>=28.0.0<28.0.2
Openstack Keystone>=29.0.0<29.0.2
debian/keystone<=2:18.0.0-3+deb11u1, <=2:22.0.2-0+deb12u1, <=2:27.0.0-3+deb13u1
2:18.1.0-1+deb11u32:22.0.2-0+deb12u32:27.0.0-3+deb13u42:29.0.1-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/keystone to a version that resolves this vulnerability.

    Fixed in 2:18.1.0-1+deb11u3Fixed in 2:22.0.2-0+deb12u3Fixed in 2:27.0.0-3+deb13u4Fixed in 2:29.0.1-2
  2. Upgrade

    Upgrade debian/keystone to a version that resolves this vulnerability.

    Fixed in 2:18.1.0-1+deb11u3
  3. Upgrade

    Upgrade debian/keystone to a version that resolves this vulnerability.

    Fixed in 2:22.0.2-0+deb12u3
  4. Upgrade

    Upgrade debian/keystone to a version that resolves this vulnerability.

    Fixed in 2:27.0.0-3+deb13u4
  5. Upgrade

    Upgrade debian/keystone to a version that resolves this vulnerability.

    Fixed in 2:29.0.1-2
  6. Configuration

    If federated identity (SAML2 or OpenID Connect) is not required, disable federated authentication to avoid exposure to the federated token rescoping issue.

    OpenStack Keystone (federated identity) federated_identity (SAML2, OpenID Connect) = disabled

Event History

May 28, 2026
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 16, 2026
Data Sourced
via Launchpad·08:41 PM
Description
Data Sourced
via Debian·08:41 PM
DescriptionAffected Software
Jun 18, 2026
Data Sourced
via Ubuntu·08:42 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-44394?

CVE-2026-44394 has a medium severity rating of 6.

2

What vulnerabilities are related to CVE-2026-44394?

CVE-2026-44394 is part of a group of vulnerabilities including CVE-2026-42998, CVE-2026-42999, CVE-2026-43000, and CVE-2026-43001.

3

How do I fix CVE-2026-44394?

To address CVE-2026-44394, upgrade OpenStack Keystone to version 29.0.2 or later.

4

What is the impact of CVE-2026-44394 on OpenStack Keystone?

CVE-2026-44394 can lead to credential delegation and authorization bypass due to improper token expiry propagation.

5

When was CVE-2026-44394 published?

CVE-2026-44394 was published on May 28, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203