← Back
CVE-2026-33551
low
CVSS 3.5
Authorization Flaw in keystone (CVE-2026-33551)
Summary
vulnerability in keystone (CVE-2026-33551). Confidential information can be exposed externally. Mitigation: upgrade to `26.1.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-33551** has been found in keystone.
Confidential information can be exposed externally. CVSS score: 3.5/10.
What to do: upgrade keystone to **26.1.1** or later.
If unsure, ask your IT team or search "keystone CVE-2026-33551" on the vendor's site.
CVE-2026-33551 (keystone) — CWE-863 / CVSS v3 3.5
Attack vector: remote (network-reachable) / no user interaction
Patched: `26.1.1` — 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
**incorrect authorization** (CWE-863) exists in keystone.
📍 Affected scope
keystone — .
🔥 Severity
Severity: Low (CVSS 3.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **26.1.1**.
🛡️ 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 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 (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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade keystone to 26.1.1ステージング環境で 26.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"14.0.0"},{"fixed":"26.1.1"}]}]
pip
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.1.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-33551
- advisory https://github.com/advisories/GHSA-4phw-6824-6cfp
- package https://github.com/openstack/keystone
- patch https://security.openstack.org/ossa/OSSA-2026-005.html
- patch http://www.openwall.com/lists/oss-security/2026/04/07/12
- report https://bugs.launchpad.net/keystone/+bug/2142138
- web https://github.com/pypa/advisory-database/tree/main/vulns/keystone/PYSEC-2026-202.yaml