# CVE-2013-3900: WinVerifyTrust Signature Validation Vulnerability > CVE-2013-3900: WinVerifyTrust Signature Validation Vulnerability. CVSS 5.5 (CVSS 3.1), in CISA KEV. Canonical: https://rewindex.com/cve/CVE-2013-3900 Last updated: 2026-10-08T16:32:16Z - Published: 2013-12-11 00:00 UTC · Updated: 2026-10-08 16:32 UTC · Assigner: microsoft - CVSS: 5.5 (CVSS 3.1) · Severity: Medium · Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C - EPSS: 44.6%, 99th percentile (scored 2026-10-25) - CISA KEV: yes, added 2022-01-10, federal due date 2022-07-10, ransomware use: Unknown - CWE: CWE-347 ## Description Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update the Security Updates table and to inform customers that the EnableCertPaddingCheck is available in all currently supported versions of Windows 10 and Windows 11. While the format is different from the original CVE published in 2013, except for clarifications about how to configure the EnableCertPaddingCheck registry value, the information herein remains unchanged from the original text published on December 10, 2013, Microsoft does not plan to enforce the stricter verification behavior as a default functionality on supported releases of Microsoft Windows. This behavior remains available as an opt-in feature via reg key setting, and is available on supported editions of Windows released since December 10, 2013. This includes all currently supported versions of Windows 10 and Windows 11. The supporting code for this reg key was incorporated at the time of release for Windows 10 and Windows 11, so no security update is required; however, the reg key must be set. See the Security Updates table for the list of affected software. Vulnerability Description A remote code execution vulnerability exists in the way that the WinVerifyTrust function handles Windows Authenticode signature verification for portable executable (PE) files. An anonymous attacker could exploit the vulnerability by modifying an existing signed executable file to leverage unverified portions of the file in such a way as to add malicious code to the file without invalidating the signature. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of this vulnerability requires that a user or application run or install a specially crafted, signed PE file. An attacker could modify an... See more at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900 ## CISA required action Apply updates per vendor instructions. ## Affected vendors and products - Microsoft: Windows 10 Version 1507 - Microsoft: Windows 10 Version 1607 - Microsoft: Windows 10 Version 1809 - Microsoft: Windows 10 Version 21H2 - Microsoft: Windows 10 Version 22H2 - Microsoft: Windows 11 version 21H2 - Microsoft: Windows 11 version 22H2 - Microsoft: Windows 11 version 22H3 - Microsoft: Windows 11 Version 23H2 - Microsoft: Windows 11 Version 24H2 - Microsoft: Windows Server 2008 R2 Service Pack 1 - Microsoft: Windows Server 2008 R2 Service Pack 1 (Server Core installation) - Microsoft: Windows Server 2008 Service Pack 2 - Microsoft: Windows Server 2008 Service Pack 2 - Microsoft: Windows Server 2008 Service Pack 2 (Server Core installation) - Microsoft: Windows Server 2012 - Microsoft: Windows Server 2012 R2 - Microsoft: Windows Server 2012 R2 (Server Core installation) - Microsoft: Windows Server 2012 (Server Core installation) - Microsoft: Windows Server 2016 - Microsoft: Windows Server 2016 (Server Core installation) - Microsoft: Windows Server 2019 - Microsoft: Windows Server 2019 (Server Core installation) - Microsoft: Windows Server 2022 - Microsoft: Windows Server 2022, 23H2 Edition (Server Core installation) - Microsoft: Windows Server 2025 - Microsoft: Windows Server 2025 (Server Core installation) ## References - [CVE record on cve.org](https://www.cve.org/CVERecord?id=CVE-2013-3900) - [NVD entry](https://nvd.nist.gov/vuln/detail/CVE-2013-3900) - [https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900) --- _Sources: CVE records from the CVE Program (cve.org). CVE® is a registered trademark of The MITRE Corporation. (https://www.cve.org/) This product uses data from the NVD API but is not endorsed or certified by the NVD. (https://nvd.nist.gov/) Known Exploited Vulnerabilities catalog from CISA. (https://www.cisa.gov/known-exploited-vulnerabilities-catalog) EPSS scores from FIRST (Exploit Prediction Scoring System). (https://www.first.org/epss/)_ --- Canonical: https://rewindex.com/cve/CVE-2013-3900 · Markdown: https://rewindex.com/cve/CVE-2013-3900.md · JSON: https://rewindex.com/api/v1/cves/CVE-2013-3900 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-10-26T02:49:18.217Z