# CVE-2026-33117: Azure SDK for Java Security Feature Bypass Vulnerability

> Attackers can bypass integrity verification in the Azure SDK for Java Key Vault Keys library by crafting encrypted input, affecting local cryptographic operations.

- **Severity:** Critical 9.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 May 2026
- **Updated:** 10 Aug 2026
- **Also known as:** CLEANSTART-2026-DU57513, CLEANSTART-2026-TC96566, CLEANSTART-2026-UN16903, CLEANSTART-2026-XK50947, ECHO-cbaa-8c1b-69db, GHSA-97jf-46m3-8953, MINI-c99g-vj9j-m8h5

## What is CVE-2026-33117?

CVE-2026-33117 is a critical vulnerability in Microsoft Azure SDK for Java, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-33117?

2 open source packages ship an affected version, including com.azure:azure-security-keyvault-keys. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.azure:azure-security-keyvault-keys` | Maven | All versions | 4.10.6 |
| `com.azure:azure-security-keyvault-keys` | Maven | All versions | 4.10.6 |

Products: Microsoft Azure Sdk for Java.

## How do I fix CVE-2026-33117?

Upgrade com.azure:azure-security-keyvault-keys to 4.10.6 or later.

## Is CVE-2026-33117 being exploited?

There is no known exploitation of CVE-2026-33117 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Azure SDK for Java

- [CVE-2020-16971](https://insights.sbomify.com/CVE-2020-16971/): Azure SDK for Java Security Feature Bypass Vulnerability (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33117 and fix it if it is affected.

What it is: CVE-2026-33117 is a critical vulnerability in Microsoft Azure SDK for Java, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33117 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.azure:azure-security-keyvault-keys (Maven): affected all versions; fixed in 4.10.6
- com.azure:azure-security-keyvault-keys (Maven): affected all versions; fixed in 4.10.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33117/ (Markdown: https://insights.sbomify.com/CVE-2026-33117/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33117
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33117
- OSV: https://osv.dev/vulnerability/CVE-2026-33117

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33117/
Summaries are generated and may contain mistakes; the official description above is the record.