CVE-2013-3900: Microsoft WinVerifyTrust function Remote Code Execution

Is it exploited?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 10 Jan 2022, 2,952 days after the CVE record was published.

How likely is exploitation in the next 30 days?

44.6%

EPSS score, percentile 98.8 of all scored records

How severe?

5.5 Medium

CVSS v3.1 base score, given by the CNA

What should I do?

CISA deadline 10 Jul 2022. Apply updates per vendor instructions.

Advisories and patches (1)

Which versions are affected?

Affected

• unspecified
• unspecified
• unspecified
• unspecified
• unspecified
• unspecified

and 14 more in the table below

Versions by product

Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of 28 Oct 2026; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of 28 Oct 2026; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.

What to do

CISA due date for this action: 10 July 2022.

Advisories and patches

• WinVerifyTrust Signature Validation Vulnerability (Vendor advisory)

Linked from CISA's catalog entry

• https://nvd.nist.gov/vuln/detail/CVE-2013-3900

Affected products and versions

As listed in the CVE record.

Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.

About this vulnerability

A remote code execution vulnerability exists in the way that the WinVerifyTrust function handles Windows Authenticode signature verification for PE files.

Summary: CISA's KEV catalog, as of 28 Oct 2026.

• CISA added CVE-2013-3900 to its Known Exploited Vulnerabilities (KEV) catalog on 10 Jan 2022.
• CISA's ransomware flag for this entry is "Unknown": no evidence of ransomware use in the catalog, which is not proof of none.
• The due date CISA sets for the required action is 10 Jul 2022.
• The CVE record was published on 11 Dec 2013, 2,952 days before it was added to KEV.
• The CVE record carries a CVSS v3.1 base score of 5.5 (Medium), given by its CNA.
• FIRST's EPSS model puts the probability of exploitation in the next 30 days at 44.6% (percentile 98.8), as of 28 Oct 2026.
• CISA's SSVC assessment in the CVE record: exploitation active, automatable no, technical impact partial.

Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of 28 Oct 2026; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of 28 Oct 2026. About the data.

Description

WinVerifyTrust Signature Validation Vulnerability

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

Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.

Weakness

• CWE-347: Improper Verification of Cryptographic Signature
• CWE-20

CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record and the KEV entry.

Timeline

More exploited Microsoft vulnerabilities

• CVE-2026-96951: Microsoft Windows Command Injection Vulnerability (added 13 Oct 2026)
• CVE-2026-65660: Microsoft SharePoint Code Injection Vulnerability (added 25 Sep 2026)
• CVE-2026-81963: Microsoft Windows Link Following Vulnerability (added 8 Sep 2026)
• CVE-2026-85880: Microsoft Windows Heap-Based Buffer Overflow Vulnerability (added 8 Sep 2026)
• CVE-2019-1068: Microsoft SQL Server Remote Code Execution Vulnerability (added 26 Aug 2026)
• CVE-2026-33824: Microsoft Internet Key Exchange (IKE) Service Extensions Double Free Vulnerability (added 18 Aug 2026)