Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2026-40683: In OpenStack Keystone before 28.0.1, the LDAP identity backend does not convert the user enabled attribute to a boolean when the user_enable

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: OpenStack Keystone 25.0.1, 26.1.1, 27.0.1.

Low priority for now. Upgrade to OpenStack Keystone 25.0.1, 26.1.1, 27.0.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.7 · v3.1—No exploit Fix available
Published
Apr 14, 2026
Updated
Aug 5, 2026
EPSS
0.3% · 27th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · mitre
7.7
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-40683

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for openstack records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

  • OpenStack Keystone

    • 8.0.0 and later · before 25.0.1affected · semver
    • 26.0.0 and later · before 26.1.1affected · semver
    • 27.0.0 and later · before 27.0.1affected · semver
    • 28.0.0 and later · before 28.0.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12keystonebefore 2:22.0.2-0+deb12u22:22.0.2-0+deb12u2
Debian:13keystonebefore 2:27.0.0-3+deb13u32:27.0.0-3+deb13u3
Debian:14keystonebefore 2:29.0.0~rc1-22:29.0.0~rc1-2
PyPIkeystonebefore 28.0.128.0.1
Red Hat:openstack:18.0::el9openstack-keystonebefore 1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost
Red Hat:openstack:18.0::el9python3-keystonebefore 1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost

Same product

openstack: all records

Other highest-scoring records for the same primary product.

  • CVE-2020-12691An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0.
    36Monitor
  • CVE-2020-12690An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0.
    36Monitor
  • CVE-2019-19687OpenStack Keystone 15.0.0 and 16.0.0 is affected by Data Leakage in the list credentials API.
    36Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-65073Nov 17, 2025 · OpenStack Keystone before 26.0.1, 27.0.0, and 28.0.0 allows a /v3/ec2tokens or /v3/s3tokens request with a valid AWS Signature to provide Ke
    30Monitor
  • ← EarlierCVE-2026-33551Apr 10, 2026 · An issue was discovered in OpenStack Keystone 14 through 26 before 26.1.1, 27.0.0, 28.0.0, and 29.0.0.
    21Monitor
  • Later →CVE-2026-43001May 1, 2026 · An issue was discovered in OpenStack Keystone before 29.0.2.
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
OpenStack Keystone25.0.1Vendor (CNA)
OpenStack Keystone26.1.1Vendor (CNA)
OpenStack Keystone27.0.1Vendor (CNA)
OpenStack Keystone28.0.1Vendor (CNA)
debian:keystone2:22.0.2-0+deb12u2 · Debian:12Package registry (OSV)
PyPI:keystone28.0.1Package registry (OSV)
red hat:openstack-keystone1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost · Red Hat:openstack:18.0::el9Package registry (OSV)
red hat:python3-keystone1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost · Red Hat:openstack:18.0::el9Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-80183134 days apartIn OpenStack Keystone before 29.0.3, any authenticated user holding role:reader on any project can list every project-scoped role assignment
    28Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
High

Weakness class (CWE)

CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records