CVE-2026-33117
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Azure SDK for Java's Key Vault Keys library has a flaw in its local cryptographic verification where the authentication tag comparison was implemented incorrectly. This allows specially crafted encrypted input to bypass integrity checks, potentially enabling tampering of encrypted data without detection. The Key Vault service-side operations are not affected.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.10.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify azure-security-keyvault-keys library presenceExamine your project's dependency management file (pom.xml for Maven or build.gradle for Gradle) for a dependency on com.azure:azure-security-keyvault-keysAffected if The library is present in the project dependencies
-
Determine installed library versionRun 'mvn dependency:tree | grep azure-security-keyvault-keys' for Maven projects, or 'gradle dependencies | grep azure-securityvault-keys' for Gradle projects to list the resolved versionAffected if The resolved version is lower than 4.10.6
-
Check if local cryptographic operations are performedReview application code for calls to CryptoAsyncClient or CryptoClient that perform local decryption operations using the library's local encryption/decryption features (not service-side only operations)Affected if The application performs local decryption of encrypted data using the Key Vault Keys library's local cryptographic verification features
Your environment is affected if the azure-security-keyvault-keys library version is below 4.10.6 AND your application uses local cryptographic operations (not exclusively service-side Key Vault operations) for decryption or encryption verification.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.10.6
Upgrade the azure-security-keyvault-keys library to version 4.10.6 or later to remediate this vulnerability.
4.10.6
- Identify all Java projects that depend on the Azure SDK for Java Key Vault Keys library
- Locate the dependency management configuration (e.g., pom.xml, build.gradle, gradle.properties) in each project
- Find the current version of the com.azure:azure-security-keyvault-keys dependency
- Update the version to 4.10.6 or later in the dependency configuration
- Rebuild and test the application to ensure the upgrade does not cause regressions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33117 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33117 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data