CVE-2026-33117: Microsoft Azure SDK for Java · Improper Authentication
Affects Microsoft Azure SDK for JavaSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.10.6 as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.10.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Microsoft Azure SDK for Java to 4.10.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MicrosoftAzure SDK for Java | Affected
| Fixed in
|
AI-suggested
An official fix is available in version 4.10.6 of the Azure SDK for Java. Users should upgrade to this version or later to remediate the vulnerability. Since this is a cloud service SDK, Microsoft manages the security of the Azure Key Vault service itself, which is not impacted. No additional mitigation steps are indicated by the vendor advisory.
Description
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.