Bug 2458472 (CVE-2026-40683) - CVE-2026-40683 OpenStack Keystone: OpenStack Keystone: Unauthorized access due to incorrect LDAP user status handling
Summary: CVE-2026-40683 OpenStack Keystone: OpenStack Keystone: Unauthorized access du...
Keywords:
Status: NEW
Alias: CVE-2026-40683
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-14 21:01 UTC by OSIDB Bzimport
Modified: 2026-07-15 09:50 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:39808 0 None None None 2026-07-15 09:50:03 UTC

Description OSIDB Bzimport 2026-04-14 21:01:52 UTC
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.

Comment 2 Marco Benatto 2026-04-16 15:24:46 UTC
Public upstream's fix for this issue :
https://review.opendev.org/c/openstack/keystone/+/958205

Comment 3 errata-xmlrpc 2026-07-15 09:50:01 UTC
This issue has been addressed in the following products:

  Red Hat OpenStack Services on OpenShift 18.0

Via RHSA-2026:39808 https://access.redhat.com/errata/RHSA-2026:39808


Note You need to log in before you can comment on or make changes to this bug.