Vulnerability in keystone (DEBIAN-CVE-2026-80182)
Summary
Vulnerability in keystone (DEBIAN-CVE-2026-80182). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2:22.0.2-0+deb12u4 or later.
Original description
The description as published by the source.
In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could create new long-lived credentials or authorize new delegations that persist independently of, and outlive, the credential used to obtain them. The delegation restrictions that block these operations did not consistently apply to all delegated token types, allowing an OAuth1-scoped token, for example, to create application credentials or authorize OAuth1 request tokens despite those operations being restricted for other delegated token types. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.
Source: OSV.dev (Open Source Vulnerabilities) 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 DEBIAN-CVE-2026-80182 has been found in keystone.
Risk of unauthorized operations or information disclosure.
What to do: upgrade keystone to 2:22.0.2-0+deb12u4 or later.
If unsure, ask your IT team or search "keystone DEBIAN-CVE-2026-80182" on the vendor's site.
DEBIAN-CVE-2026-80182 (keystone)
Patched: 2:22.0.2-0+deb12u4 — 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.
A vulnerability (unclassified) exists in keystone.
Check the vendor advisory for the affected versions of keystone.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2:22.0.2-0+deb12u4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'keystone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
keystoneを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade keystone to 2:22.0.2-0+deb12u4ステージング環境で 2:22.0.2-0+deb12u4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory security-tracker.debian.org