Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

An issue was discovered in OpenStack Keystone 13 through 29. POST /v3/credentials did not validate that the caller-supplied project_id for an EC2-type credential matched the project of the authenticating application credential. This allowed an attacker holding an unrestricted application credential for project A to create an EC2 credential targeting project B; a subsequent /v3/ec2tokens exchange would then issue a Keystone token scoped to project B while still carrying the original app_cred_id, enabling cross-project lateral movement within the credential owner's role footprint.

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-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.

📍 Affected scope

Check the vendor advisory for the affected versions of 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

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
    Hunt 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 があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against POST /v3/credentials on staging to confirm patch closes the vector

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

Affected packages

PyPI keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"13.0.0"},{"last_affected":"29.0.1"}]}]
pip keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

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