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.
Original description
The description as published by the source.
The Java Key Vault Keys library in the Azure SDK for Java contains an issue in the local cryptographic verification path where authentication tag comparison was implemented incorrectly. In affected applications that use the vulnerable local cryptography path, specially crafted encrypted input may bypass integrity verification checks. Operations delegated to the Key Vault service are not affected. The issue is addressed in version 4.10.6.
Source: GitHub Security Advisories (Global) 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-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.
Authentication bypass (CWE-287) exists in com.azure:azure-security-keyvault-keys.
Check the vendor advisory for the affected versions of com.azure:azure-security-keyvault-keys.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to 4.10.6.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.azure:azure-security-keyvault-keys を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.azure:azure-security-keyvault-keys to 4.10.6ステージング環境で 4.10.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory msrc.microsoft.com
- package github.com
- web github.com
- web github.com
- web github.com