Authorization Flaw in keystone (CVE-2026-44394)
Summary
Vulnerability in keystone (CVE-2026-44394). Risk of unauthorized operations or information disclosure. Exploitable via POST /v3/auth/tokens. Mitigation: upgrade to 29.0.2 or later.
Original description
The description as published by the source.
An issue was discovered in OpenStack Keystone before 29.0.2. The Keystone federated token rescoping mechanism does not propagate the original token's expiry to the newly issued token. When a federated user rescopes a token via POST /v3/auth/tokens, the handle_scoped_token() function in the mapped authentication plugin returns response data without an expires_at value. The token provider falls back to issuing a token with a fresh default TTL. By rescoping repeatedly before each token expires, a user can maintain access indefinitely, bypassing operator-configured token lifetime policies. This is a variant of CVE-2012-3426. Only deployments using federated identity (SAML2, OpenID Connect) are affected.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-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: 6.0/10.
What to do: upgrade keystone to 29.0.2 or later.
If unsure, ask your IT team or search "keystone CVE-2026-44394" on the vendor's site.
CVE-2026-44394 (keystone) — CWE-863 / CVSS v3 6.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /v3/auth/tokens
Patched: 29.0.2 — 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.
Incorrect authorization (CWE-863) exists in keystone. Attackers reach the vulnerable code path via POST /v3/auth/tokens.
Check the vendor advisory for the affected versions of keystone. Attack surface: POST /v3/auth/tokens.
Severity: Medium (CVSS 6.0/10). Risk of unauthorized operations or information disclosure.
Update to 29.0.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt 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 があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade keystone to 29.0.2ステージング環境で 29.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /v3/auth/tokens on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-44394 keystone Fixed in: 2:18.1.0-1+deb11u3
- Ubuntu UBUNTU-CVE-2026-44394 keystone
References
- advisory nvd.nist.gov
- package github.com
- web bugs.launchpad.net
- web security.openstack.org
- web github.com
- web github.com