https://seclists.org/oss-sec/2026/q3/573: [OSSA-2026-037] OpenStack Keystone: Inconsistent scope enforcement for delegated tokens (CVE-2026-pending)

Published Aug 25, 2026
·
Updated

Affected Software

1 affected component
Openstack Keystone>13.0.0<27.0.3, >28.0.0<28.0.3, >29.0.0<29.0.3

Frequently Asked Questions

1

Which Keystone releases need remediation?

Affected releases are Keystone >=13.0.0 and <27.0.3, >=28.0.0 and <28.0.3, and >=29.0.0 and <29.0.3.

2

Which delegation mechanisms can be used in the affected flows?

The affected delegated-token flows include tokens scoped through an OAuth1 access token, an application credential, or a trust.

3

What can an attacker retain after using a delegated token?

A delegated token could create long-lived credentials or authorize new delegations. Those newly created credentials or delegations can persist independently of, and outlive, the credential used to obtain them.

4

When can an application credential token escape its intended project scope?

When an application credential token is submitted to the token-method authentication path without an explicit scope, Keystone can issue a new token scoped to the credential owner's default project.

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