← Back
UBUNTU-CVE-2026-44394
Vulnerability in keystone (UBUNTU-CVE-2026-44394)
Summary
vulnerability in keystone (UBUNTU-CVE-2026-44394). Risk of unauthorized operations or information disclosure. Exploitable via `POST /v3/auth/tokens`. Mitigation: upgrade to `2:21.0.1-0ubuntu2.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2026-44394** has been found in keystone.
Attackers can target a specific entry point like `POST /v3/auth/tokens` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade keystone to **2:21.0.1-0ubuntu2.4** or later.
If unsure, ask your IT team or search "keystone UBUNTU-CVE-2026-44394" on the vendor's site.
UBUNTU-CVE-2026-44394 (keystone) —
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /v3/auth/tokens
Patched: `2:21.0.1-0ubuntu2.4` — 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** (unclassified) exists in keystone. Attackers reach the vulnerable code path via `POST /v3/auth/tokens` without authentication.
📍 Affected scope
keystone — . Attack surface: POST /v3/auth/tokens.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2:21.0.1-0ubuntu2.4**.
🛡️ 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/auth/tokens` 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/auth/tokens' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /v3/auth/tokens` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade keystone to 2:21.0.1-0ubuntu2.4ステージング環境で 2:21.0.1-0ubuntu2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /v3/auth/tokens on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:16.04:LTS
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:18.04:LTS
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:Pro:20.04:LTS
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:22.04:LTS
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:21.0.1-0ubuntu2.4"}]}]
Ubuntu:24.04:LTS
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:25.0.0-0ubuntu1.4"}]}]
Ubuntu:25.10
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:28.0.0-0ubuntu1.3"}]}]
Ubuntu:26.04:LTS
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:29.0.0-0ubuntu1.2"}]}]