CVE-2015-7546: OpenStack Keystone Identity Service Token Bypass
Summary
CVE-2015-7546: The identity service in OpenStack Identity (Keystone) before 2015.1.3 (Kilo) and 8.0.x before 8.0.2 (Liberty) and keystonemiddleware (formerly python-keystoneclient) before 1.5.4 (Kilo) and Liberty before 2.3.3 does not... Affects keystonemiddleware across 2 version ranges.
< 1.5.4
>= 1.6.0, < 2.3.3
Fixed in 1.5.4 or 2.3.3, depending on the release line you run. How to fix ↓
Also tracked for
The same CVE-2015-7546 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
OpenStack Identity (Keystone) is an open-source service that provides authentication and authorization for other OpenStack services. It manages user credentials and provides a catalog of available services. Keystone uses tokens to authenticate and authorize users. The keystonemiddleware (formerly python-keystoneclient) is a Python library that provides middleware for integrating Keystone with other applications. This vulnerability affects Keystone versions before 2015.1.3 (Kilo) and 8.0.x before 8.0.2 (Liberty), as well as keystonemiddleware versions before 1.5.4 (Kilo) and Liberty before 2.3.3.
Vulnerability Detail
The vulnerability in Keystone and keystonemiddleware arises from the improper invalidation of authorization tokens when using the PKI or PKIZ token providers. This flaw allows remote authenticated users to bypass access restrictions and gain unauthorized access to cloud resources by manipulating byte fields within a revoked token. An attacker with a revoked token can modify certain byte fields to make the token appear valid and gain access to resources they should not have permission to access. This can lead to unauthorized data access, privilege escalation, and potential compromise of the entire cloud infrastructure.
How To Fix
Latest published version: 13.0.1 as of 22 Oct 2026
pip install --upgrade "keystonemiddleware==13.0.1"Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.5.41.5.4pip install --upgrade "keystonemiddleware==1.5.4" -
>= 1.6.0, < 2.3.32.3.3pip install --upgrade "keystonemiddleware==2.3.3"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. It is recommended to apply the fix by upgrading to the fixed versions.
Conclusion
The vulnerability in OpenStack Keystone Identity Service and keystonemiddleware allows remote authenticated users to bypass access restrictions and gain unauthorized access to cloud resources. It is crucial to upgrade to the fixed versions to mitigate the risk of unauthorized data access and potential compromise of the cloud infrastructure. For further support on vulnerability remediation, contact DevNack.com.
See every vulnerability recorded for keystonemiddleware →
FAQ
OpenStack Identity (Keystone) is an open-source service that provides authentication and authorization for other OpenStack services. It manages user credentials and provides a catalog of available services.
keystonemiddleware (formerly python-keystoneclient) is a Python library that provides middleware for integrating Keystone with other applications.
This vulnerability allows remote authenticated users to bypass access restrictions and gain unauthorized access to cloud resources. It can lead to unauthorized data access, privilege escalation, and potential compromise of the entire cloud infrastructure.
To fix this vulnerability, upgrade to the fixed versions of Keystone and keystonemiddleware. Upgrade to Keystone version 2015.1.3 (Kilo) or 8.0.2 (Liberty), and upgrade to keystonemiddleware version 1.5.4 (Kilo) or 2.3.3 (Liberty).
There is no specific workaround mentioned for this vulnerability. It is recommended to apply the fix by upgrading to the fixed versions.
Related vulnerabilities
Recent vulnerabilities recorded for keystonemiddleware.
