← Back
CVE-2026-43001
high
CVSS 7.9
Authorization Flaw in keystone (CVE-2026-43001)
Summary
vulnerability in keystone (CVE-2026-43001). Confidential information can be exposed externally. Exploitable via `POST /v3/credentials`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-43001** has been found in keystone.
Attackers can target a specific entry point like `POST /v3/credentials` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "keystone CVE-2026-43001" on the vendor's site.
CVE-2026-43001 (keystone) — CWE-863 / CVSS v3 7.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /v3/credentials
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
**incorrect authorization** (CWE-863) exists in keystone. Attackers reach the vulnerable code path via `POST /v3/credentials` without authentication.
📍 Affected scope
keystone — . Attack surface: POST /v3/credentials.
🔥 Severity
Severity: High (CVSS 7.9/10). Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 `POST /v3/credentials` requests with malformed payloads or SQL meta-characters. Run `grep -r 'keystone' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'keystone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `keystone` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /v3/credentials' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /v3/credentials` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against POST /v3/credentials on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"13.0.0"},{"last_affected":"29.0.1"}]}]
pip
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-43001
- exploit [email protected]
- package https://review.opendev.org/c/openstack/keystone
- patch [email protected]
- patch [email protected]
- web https://github.com/advisories/GHSA-hhq2-3832-xxcv
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c