GHSA-pfx2-9x9m-7ghx CVE-2026-40683 PYSEC-2026-2550
OpenStack Keystone: LDAP identity backend does not convert enabled attribute to boolean
- Severity
- 7.7 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.34%
- Chance of exploitation in the next 30 days. Higher than 27.16% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')
- Fix
28.0.1- Upgrade keystone to this version or later
Description
In OpenStack Keystone before 28.0.1, the LDAP identity backend does not convert the user enabled attribute to a boolean when the user_enabled_invert configuration option is False (the default). The _ldap_res_to_model method in the UserApi class only performed string-to-boolean conversion when user_enabled_invert was True. When False, the raw string value from LDAP (e.g., "FALSE") was used directly. Since non-empty strings are truthy in Python, users marked as disabled in LDAP were treated as enabled by Keystone, allowing them to authenticate and perform actions. All deployments using the LDAP identity backend without user_enabled_invert=True or user_enabled_emulation are affected.
Affected versions
PyPI
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
keystone PyPI → 28.0.1
- pip
pip install --upgrade "keystone>=28.0.1"- poetry
poetry add "keystone>=28.0.1"- uv
uv add "keystone>=28.0.1"
Severity breakdown
CVSS 3.1 7.7
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
Weakness
CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-whqr-fgm5-x77q OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token | High | Also affects keystone |
| GHSA-q623-f4j4-p4xj OpenStack Keystone has an Incorrect Authorization issue | High | Also affects keystone |
| GHSA-2r23-2g6v-2m5f OpenStack Keystone has an Authorization Bypass | High | Also affects keystone |
| GHSA-8f8m-wrvr-wcvf OpenStack Keystone doesn't verify that the user supplied in the authentication request matches the owner of the application credential | High | Also affects keystone |
| GHSA-hhq2-3832-xxcv OpenStack Keystone has an Incorrect Authorization Issue | High | Also affects keystone |
| GHSA-4phw-6824-6cfp OpenStack Keystone: Restricted application credentials can create EC2 credentials | Medium | Also affects keystone |
| GHSA-hcqg-5g63-7j9h OpenStack Keystone allows /v3/ec2tokens or /v3/s3tokens request with valid AWS Signature to provide Keystone authorization. | High | Also affects keystone |
| GHSA-cc99-whm5-mmq3 Openstack Keystone Incorrect Authorization vulnerability | Critical | Also affects keystone |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor