Integrity bypass via self-comparison of authentication tag
Published May 12, 2026 · Updated May 12, 2026
Improper authentication in Azure Key Vault Keys for Java before 4.10.6 allows remote attackers to bypass encrypted-data integrity checks. AesCbcHmacSha2Decryptor.doFinal compares the computed authentication tag with itself instead of the received tag, so altered ciphertext is accepted. Reachability requires an application to process attacker-controlled ciphertext with local cryptography; Key Vault service operations are unaffected.
Summary
What happened
Improper authentication in Azure Key Vault Keys for Java before 4.10.6 allows remote attackers to bypass encrypted-data integrity checks. AesCbcHmacSha2Decryptor.doFinal compares the computed authentication tag with itself instead of the received tag, so altered ciphertext is accepted. Reachability requires an application to process attacker-controlled ciphertext with local cryptography; Key Vault service operations are unaffected.
The record
- CVE
- CVE-2026-33117
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Microsoft
- Product
- Azure SDK for Java
- Classifications
- CWE-287, CWE-347, T1565
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <4.10.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo