Skip to main content
VulnerabilityPublished Updated

CVE-2026-40683: OpenStack Keystone · Type Confusion

Affects OpenStack KeystoneSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High · fixed in 28.0.1 : patch OpenStack Keystone soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 28.0.1, 27.0.1, 26.1.1 +1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade OpenStack Keystone to 28.0.1, 27.0.1, 26.1.1 or 25.0.1.

Affected software

ProductAffectedFixed in
OpenStackKeystoneAffected
  • >=28.0.0 <28.0.1
Fixed in
  • 28.0.1
OpenStackKeystoneAffected
  • >=27.0.0 <27.0.1
Fixed in
  • 27.0.1
OpenStackKeystoneAffected
  • >=26.0.0 <26.1.1
Fixed in
  • 26.1.1
OpenStackKeystoneAffected
  • >=8.0.0 <25.0.1
Fixed in
  • 25.0.1
PyPIkeystonepkg:pypi/keystoneOther threatsAffected
  • 8.0.0 – 28.0.0
4 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, deployments should consider setting the user_enabled_invert configuration option to True or enabling user_enabled_emulation as a temporary mitigation to ensure proper boolean conversion of the user enabled attribute. Monitor vendor communications for an official patch or update.

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.

References

Community reviews

Loading reviews…