CVE-2026-33117: The Java Key Vault Keys library in the Azure SDK for Java contains an issue in the local cryptographic verific

Q: How do I fix CVE-2026-33117?

azure sdk for java: upgrade to 4.10.6. Exact commands for each OS are on this page.

Q: Is CVE-2026-33117 being exploited?

CVE-2026-33117 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-33117 affect?

CVE-2026-33117 affects azure sdk for java. Severity is critical (CVSS 9.1). 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

Q: How urgent is CVE-2026-33117?

Priority 52/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

This month

CRITICAL 9.1REMOTEWATCHLISTUPGRADE

CVE-2026-33117 is a critical-severity flaw (CVSS 9.1) affecting azure sdk for java. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.1 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-287, CWE-347
Published	2026-05-12
Last modified	2026-10-26

Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-12 18:17 UTCPublished CVE record published
2026-10-26 18:10 UTCUpdated Record last modified

microsoft azure sdk for java UPGRADE

Affected: < 4.10.6

Fixed in: 4.10.6

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy azure-sdk-for-java || rpm -q azure-sdk-for-java || azure-sdk-for-java --version

2. UPGRADE to 4.10.6 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade azure-sdk-for-java

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade azure-sdk-for-java

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-33117?

azure sdk for java: upgrade to 4.10.6. Exact commands for each OS are on this page.

Is CVE-2026-33117 being exploited?

CVE-2026-33117 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-33117 affect?

CVE-2026-33117 affects azure sdk for java. Severity is critical (CVSS 9.1). 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

How urgent is CVE-2026-33117?

Priority 52/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Java vulnerabilities · Azure vulnerabilities · HashiCorp Vault vulnerabilities

References

← Back to latest CVEs