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.
Original description
The description as published by the source.
An issue was discovered in OpenStack Keystone 14 through 26 before 26.1.1, 27.0.0, 28.0.0, and 29.0.0. Restricted application credentials can create EC2 credentials. By using a restricted application credential to call the EC2 credential creation API, an authenticated user with only a reader role may obtain an EC2/S3 credential that carries the full set of the parent user's S3 permissions, effectively bypassing the role restrictions imposed on the application credential. Only deployments that use restricted application credentials in combination with the EC2/S3 compatibility API (swift3 / s3api) 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-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.
Incorrect authorization (CWE-863) exists in keystone.
Check the vendor advisory for the affected versions of keystone.
Severity: Low (CVSS 3.5/10). Confidential information can be exposed externally.
Update to 26.1.1.
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 26.1.1ステージング環境で 26.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-33551 keystone Fixed in: 2:18.1.0-1+deb11u3
- Ubuntu UBUNTU-CVE-2026-33551 keystone
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch security.openstack.org
- patch openwall.com
- report bugs.launchpad.net
- web github.com