CVE-2026-35199 Details
Description
SymCrypt is the core cryptographic function library currently used by Windows. From 103.5.0 to before 103.11.0, The SymCryptXmssSign function passes a 64-bit leaf count value to a helper function that accepts a 32-bit parameter. For XMSS^MT parameter sets with total tree height >= 32 (which includes standard predefined parameters), this causes silent truncation to zero, resulting in a drastically undersized scratch buffer allocation followed by a heap buffer overflow during signature computation. Exploiting this issue would require an application using SymCrypt to perform an XMSS^MT signature using an attacker-controlled parameter set. It is uncommon for applications to allow the use of attacker-controlled parameter sets for signing, since signing is a private key operation, and private keys must be trusted by definition. Additionally, XMSS(^MT) signing should only be performed in a Hardware Security Module (HSM). XMSS(^MT) signing is provided in SymCrypt only for testing purposes. This is a general rule irrespective of this CVE; XMSS(^MT) and other stateful signature schemes are only cryptographically secure when it is guaranteed that the same state cannot be reused for two different signatures, which cannot be guaranteed by software alone. For this reason, XMSS(^MT) signing is also not FIPS approved when performed outside of an HSM. Fixed in version 103.11.0.
A heap buffer overflow vulnerability has been identified in the SymCrypt library, specifically in the SymCryptXmssSign function. This issue arises in versions 103.5.0 prior to 103.11.0. The vulnerability is caused by the function passing a 64-bit leaf count value to a helper that only accepts a 32-bit parameter. In XMSS^MT parameter sets with a total tree height of 32 or more, this leads to a silent truncation of the value to zero. Consequently, this creates a significantly undersized scratch buffer allocation, which is followed by a heap buffer overflow during the signature computation process. Exploitation of this vulnerability would require an application to use SymCrypt for XMSS^MT signing with an attacker-controlled parameter set. Such a scenario is rare, as signing operations involve private keys that must be trusted. Furthermore, XMSS(^MT) signing should only be conducted within a Hardware Security Module (HSM). In SymCrypt, XMSS(^MT) signing is available solely for testing purposes.
Users can upgrade to SymCrypt version 103.11.0 to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 7, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/microsoft/SymCrypt/security/advisories/GHSA-rvj8-8h6x-hjmg | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-122 | Heap-based Buffer Overflow | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| microsoft symcrypt | >= 103.5.0, < 103.11.0 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 24, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 16, 2026 | Initial Analysis | [email protected] |
| Apr 6, 2026 | New CVE Received | [email protected] |