Access of Resource Using Incompatible Type ('Type Confusion') Affecting keystone package, versions [,26.1.1)[27.0.0.0rc1,27.0.1)[28.0.0.0rc1,28.0.1)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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 applicationsSnyk Learn
Learn about Access of Resource Using Incompatible Type ('Type Confusion') vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-KEYSTONE-16083778
- published16 Apr 2026
- disclosed14 Apr 2026
- creditBenedikt Trefzer, Andrew Bogott, Grzegorz Grasza
Introduced: 14 Apr 2026
CVE-2026-40683 (opens in a new tab)How to fix?
Upgrade keystone to version 26.1.1, 27.0.1, 28.0.1 or higher.
Overview
keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family.
Affected versions of this package are vulnerable to Access of Resource Using Incompatible Type ('Type Confusion') via the UserApi._ldap_res_to_model function in keystone/identity/backends/ldap/core.py. An attacker can gain unauthorized access and perform privileged actions by exploiting improper handling of the enabled attribute from LDAP, which may allow users marked as disabled to be treated as enabled. When user_enabled_invert is not in use, the LDAP backend still coerces the enabled attribute using inversion logic, so users can be treated as enabled or disabled, contrary to the directory value. This can either keep disabled LDAP accounts usable or cause valid accounts to be rejected, breaking login and account access for Keystone users.
Notes
- This only affects deployments that rely on the LDAP backend with
user_enabled_invert=Falseand do not useuser_enabled_emulation.