← Back
CVE-2026-33117
critical
CVSS 9.1
Authentication Bypass in com.azure:azure-security-keyvault-keys (CVE-2026-33117)
Summary
authentication bypass in com.azure:azure-security-keyvault-keys (CVE-2026-33117). Confidential information can be exposed externally. Mitigation: upgrade to `4.10.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-33117** has been found in com.azure:azure-security-keyvault-keys.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade com.azure:azure-security-keyvault-keys to **4.10.6** or later.
If unsure, ask your IT team or search "com.azure:azure-security-keyvault-keys CVE-2026-33117" on the vendor's site.
CVE-2026-33117 (com.azure:azure-security-keyvault-keys) — CWE-287 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `4.10.6` — 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
**authentication bypass** (CWE-287) exists in com.azure:azure-security-keyvault-keys.
📍 Affected scope
com.azure:azure-security-keyvault-keys — .
🔥 Severity
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **4.10.6**.
🛡️ 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 'com.azure:azure-security-keyvault-keys' .` 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 'com.azure:azure-security-keyvault-keys' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `com.azure:azure-security-keyvault-keys` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade com.azure:azure-security-keyvault-keys to 4.10.6ステージング環境で 4.10.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
com.azure:azure-security-keyvault-keys
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.10.6"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-33117
- package https://github.com/Azure/azure-sdk-for-java
- web https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33117
- web https://github.com/advisories/GHSA-97jf-46m3-8953
- web https://github.com/Azure/azure-sdk-for-java/pull/48476
- web https://github.com/Azure/azure-sdk-for-java/commit/1b5c5c79d85a5c9a9cfd07f6cdff6fd0f50eccf9