Encryption-protection bypass in EncryptedXml
Published Jul 14, 2026 · Updated Jul 14, 2026
Improper signature verification in Microsoft Visual Studio 2022 and 2026 allows remote attackers to bypass XML encryption protections. Microsoft identifies the affected locus as the System.Security.Cryptography.Xml EncryptedXml implementation but has not disclosed the incorrect verification operation. Exploitation requires a project or application to use affected XML cryptography code; it needs no credentials or user interaction and allows access to encrypted data.
Summary
What happened
Improper signature verification in Microsoft Visual Studio 2022 and 2026 allows remote attackers to bypass XML encryption protections. Microsoft identifies the affected locus as the System.Security.Cryptography.Xml EncryptedXml implementation but has not disclosed the incorrect verification operation. Exploitation requires a project or application to use affected XML cryptography code; it needs no credentials or user interaction and allows access to encrypted data.
The record
- CVE
- CVE-2026-47304
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2022 version 17.12
- Classifications
- CWE-347, CWE-345
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 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=17.12.0 <17.12.22
What conditions does exploitation require?
What is affected?
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