CVE-2013-3900

published 11 Dec 2013 · updated 8 Oct 2026

WinVerifyTrust Signature Validation Vulnerability

8.0HighCVSS 5.5EPSS 45%CISA KEV · due 10 Jul 2022Zero-day

Exploited in the wild as a zero-day, in CISA KEV since 10 Jan 2022 (due 10 Jul 2022). No fixed version is recorded.

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

Briefing

Written from the sources below · deepseek-v4.1-flash

CVE-2013-3900 is a remote code execution vulnerability in how WinVerifyTrust handles Authenticode signature verification of PE files, letting an attacker modify a signed executable to exploit unverified portions. Microsoft is republishing it to note that the opt-in EnableCertPaddingCheck registry value exists in all currently supported Windows 10 and Windows 11 versions.

Why it mattersIt is in CISA KEV with confirmed exploitation and EPSS 45%, yet Microsoft will not enforce stricter verification by default, leaving unconfigured systems exposed.

ActionSet the EnableCertPaddingCheck registry value; no security update is required for supported Windows 10 and 11 releases.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
MicrosoftWinVerifyTrust function
MicrosoftWindows

Exploit evidence

1 public sources

kev

Timeline

Every event on this vulnerability

Added to CISA KEVCVE-2013-3900·
CVE-2013-3900 is a remote code execution vulnerability in how WinVerifyTrust handles Authenticode signature verification of PE files, letting an attacker modify a signed executable to exploit unverified portions. Microsoft is republishing it to note that the opt-in EnableCertPaddingCheck registry value exists in all currently supported Windows 10 and Windows 11 versions.
7.0High
PublishedCVE-2013-3900·
CVE-2013-3900 is a remote code execution vulnerability in how WinVerifyTrust handles Authenticode signature verification of PE files, letting an attacker modify a signed executable to exploit unverified portions. Microsoft is republishing it to note that the opt-in EnableCertPaddingCheck registry value exists in all currently supported Windows 10 and Windows 11 versions.
7.0High
Zero-dayCVE-2013-3900·
CVE-2013-3900 is a remote code execution vulnerability in how WinVerifyTrust handles Authenticode signature verification of PE files, letting an attacker modify a signed executable to exploit unverified portions. Microsoft is republishing it to note that the opt-in EnableCertPaddingCheck registry value exists in all currently supported Windows 10 and Windows 11 versions.
8.0High

Related

Other vulnerabilities in Windows, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2013-3900 severity on Zeptric[![CVE-2013-3900](https://zeptric.io/badge/cve/CVE-2013-3900.svg)](https://zeptric.io/cve/CVE-2013-3900)