Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-40683 high CVSS 7.7

Vulnerability in keystone (CVE-2026-40683)

Summary

Vulnerability in keystone (CVE-2026-40683). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 28.0.1 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-40683 has been found in keystone.
Risk of unauthorized operations or information disclosure. CVSS score: 7.7/10.
What to do: upgrade keystone to 28.0.1 or later.
If unsure, ask your IT team or search "keystone CVE-2026-40683" on the vendor's site.

CVE-2026-40683 (keystone) — CWE-843 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 28.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-843) exists in keystone.

📍 Affected scope

Check the vendor advisory for the affected versions of keystone.

🔥 Severity

Severity: High (CVSS 7.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 28.0.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'keystone' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'keystone' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で keystone を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade keystone to 28.0.1

    ステージング環境で 28.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"28.0.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details