Security Digest · Vulnerability record
CVE-2026-33117: Security feature bypass vulnerability in Azure Key Vault Keys library for Java
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.
CVSS 9.1 Critical EPSS 0.5% · p42
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.5%, percentile 42: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 42% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
com.azure:azure-security-keyvault-keys(Maven) < 4.10.6, fixed in 4.10.6. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
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.
Weakness type: CWE-287, CWE-347.
Product: com.azure:azure-security-keyvault-keys (Maven) · Assigned by: microsoft · Published: 2026-05-12
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Maven | com.azure:azure-security-keyvault-keys | < 4.10.6 | 4.10.6 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| Microsoft | Azure SDK for Java | 1.0.0 < 4.10.6 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| microsoft | 3.1 | 9.1 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: none
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-10-21): 0.50% probability of exploitation activity in the next 30 days; percentile 42.
Timeline
- — CVE record published by microsoft
- — GitHub-reviewed advisory GHSA-97jf-46m3-8953 published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vendor and project advisories, patches
- Azure SDK for Java Security Feature Bypass Vulnerability msrc.microsoft.com
Vulnerability records
- GitHub Advisory GHSA-97jf-46m3-8953 github.com
- CVE.org record CVE-2026-33117 cve.org
- NVD entry CVE-2026-33117 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com