Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to vulnerabilities
Critical

Improper authentication tag verification in Azure Key Vault Keys library for Java

IdentifiersCVE-2026-33117CWE-347· Improper Verification of…

CVE-2026-33117 affects the Java Key Vault Keys library in the Azure SDK for Java. The flaw is in the local cryptographic verification path, where authentication tag comparison was implemented incorrectly. As a result, affected Java applications that perform local cryptographic operations through this vulnerable path may accept specially crafted encrypted input without properly detecting tampering. This is a security feature bypass affecting integrity verification of encrypted data. Microsoft and related advisory material state that operations delegated to the Azure Key Vault service are not affected. The issue is fixed in com.azure:azure-security-keyvault-keys version 4.10.6.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthorized attacker to bypass the integrity protection enforced by the authentication tag during local cryptographic verification. In practical terms, tampered encrypted input may be treated as valid by the affected application, undermining trust in the authenticity and integrity of protected data. The available advisory material indicates high confidentiality and integrity impact, with no stated availability impact. This does not affect operations performed by the Key Vault service itself; the exposure is limited to applications using the vulnerable local cryptography path.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, avoid relying on the vulnerable local cryptographic verification path in affected Java applications. Prefer cryptographic operations delegated to the Azure Key Vault service, which Microsoft states are not affected by this issue. Review application code paths to identify where local verification is used and reduce or disable that usage until patched.

Remediation

Patch, then assume compromise.

Upgrade the Azure SDK for Java Key Vault Keys package com.azure:azure-security-keyvault-keys to version 4.10.6 or later. More generally, apply the official Microsoft fix for CVE-2026-33117 and redeploy affected Java applications so they no longer use the vulnerable implementation.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationAzure Sdkapplication
Microsoft CorporationAzure Sdk For Javaapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

4 SOURCESView more in app
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-33117
NVD
nvd.nist.gov/vuln/detail/CVE-2026-33117
MITRE CWE · CWE-347
Improper Verification of Cryptographic Signature
Vendor Advisory
msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33117