Service interruption via EncryptedXml stack overflow
Published Apr 14, 2026 · Updated Apr 14, 2026
Stack-based buffer overflow in EncryptedXml in Microsoft .NET and Visual Studio allows remote attackers to interrupt services over a network. Microsoft identifies the locus as the System.Security.Cryptography.Xml EncryptedXml class but has not disclosed which input or write operation overruns the stack buffer. Unauthenticated network access is sufficient; successful exploitation interrupts the process without reported confidentiality or integrity impact.
Summary
What happened
Stack-based buffer overflow in EncryptedXml in Microsoft .NET and Visual Studio allows remote attackers to interrupt services over a network. Microsoft identifies the locus as the System.Security.Cryptography.Xml EncryptedXml class but has not disclosed which input or write operation overruns the stack buffer. Unauthenticated network access is sufficient; successful exploitation interrupts the process without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2026-32203
- Published
- Apr 14, 2026
- Updated
- Apr 14, 2026
- Vendor
- Microsoft
- Product
- .NET 9.0
- Classifications
- CWE-121, CWE-20, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2026CVE publishedPublication date reported by the CVE source.
- Apr 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=9.0.0 <9.0.15
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