Security readout for executives and security teams
Plain-English summary
Affected Java applications may accept tampered encrypted data as authentic because a local integrity check compares authentication tags incorrectly. This can expose or corrupt sensitive information. Azure Key Vault service operations are unaffected. The source bundle states the issue is fixed in version 4.10.6.
Executive priority
Treat as an urgent, targeted remediation. Immediately identify internet-facing or externally fed applications using local Key Vault Keys cryptography, then upgrade them. Service-delegated Key Vault operations are outside the described impact, allowing teams to focus effort on confirmed local-path usage.
Technical view
CVE-2026-33117 affects the Azure SDK for Java Key Vault Keys library’s local cryptographic verification path. Crafted encrypted input may bypass authentication-tag verification, undermining confidentiality and integrity without affecting availability. CVSS 3.1 is 9.1: network-accessible, low complexity, unauthenticated, and requiring no user interaction.
Likely exposure
Exposure requires an application using the vulnerable local cryptography path and processing attacker-controlled encrypted input. Applications delegating operations to Azure Key Vault are not affected. The bundle lists version 1.0.0 but does not define the complete affected range, so dependency-level confirmation is necessary.
Exploitation context
The source bundle does not cite active exploitation, and the CVE is not listed as KEV. Its CVSS vector records exploit maturity as unproven. Nevertheless, unauthenticated, low-complexity input handling and potentially severe confidentiality and integrity impact justify urgent remediation where the local path is reachable.
Researcher notes
CWE-287 and CWE-347 describe authentication and cryptographic-signature verification weaknesses. The key condition is an incorrect authentication-tag comparison in local verification. The bundle does not specify algorithms, exact affected version ranges, exploit availability, or implementation details; those points should not be inferred.
Mitigation direction
- Upgrade the Java Key Vault Keys library to version 4.10.6 or later vendor-approved release.
- Prioritize applications using local cryptographic operations on externally supplied encrypted data.
- Where upgrading is delayed, avoid the affected local verification path when operationally feasible.
- Review Microsoft guidance for any additional affected-version or mitigation details.
Validation and detection
- Inventory Java applications and resolve the installed Key Vault Keys library version.
- Confirm whether each application uses local cryptographic verification or delegates operations to Key Vault.
- Identify whether untrusted encrypted input can reach the local verification path.
- After upgrading, verify dependency lockfiles and deployed artifacts resolve version 4.10.6 or later.
- Run defensive integrity tests confirming modified ciphertext is rejected without exposing sensitive data.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-33117 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C3.95.2microsoftVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Azure SDK for Java Security Feature Bypass VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.