Skip to main content
CISA Known Exploited Vulnerabilities

Microsoft WinVerifyTrust function Remote Code Execution is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2022-01-10
Remediation due
2022-07-10

Required action
Apply updates per vendor instructions.

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

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

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2013-3900 to the KEV catalog 2,952 days after its CVE record was published.
  • It is one of 392 Microsoft entries in the CISA KEV catalog, and one of 166 added in 2022.
  • Its current EPSS score (44.6%) is higher than that of 46% of CISA KEV entries.

Severity

CVSS 3.1 · CNA · Base score5.5 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N/E:U/RL:O/RC:COpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableno
Technical impactpartial

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
14 days
Asset not publicly exposed
14 days
KEV due date
2022-07-10
181 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact partial, 2025-02-10).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
Microsoft
Windows 10 Version 1809
N/A
Microsoft
Windows 10 Version 1809
N/A
Microsoft
Windows Server 2019
N/A
Microsoft
Windows Server 2019 (Server Core installation)
N/A
Microsoft
Windows Server 2022
N/A
Microsoft
Windows 11 version 21H2
N/A
Microsoft
Windows 10 Version 21H2
N/A
Microsoft
Windows 11 version 22H2
N/A
Microsoft
Windows 10 Version 22H2
N/A
Microsoft
Windows Server 2025 (Server Core installation)
N/A
Microsoft
Windows 11 version 22H3
N/A
Microsoft
Windows 11 Version 23H2
N/A
Microsoft
Windows Server 2022, 23H2 Edition (Server Core installation)
N/A
Microsoft
Windows 11 Version 24H2
N/A
Microsoft
Windows Server 2025
N/A
Microsoft
Windows 10 Version 1507
N/A
Microsoft
Windows 10 Version 1607
N/A
Microsoft
Windows Server 2016
N/A
Microsoft
Windows Server 2016 (Server Core installation)
N/A
Microsoft
Windows Server 2008 Service Pack 2
N/A
Microsoft
Windows Server 2008 Service Pack 2 (Server Core installation)
N/A
Microsoft
Windows Server 2008 Service Pack 2
N/A
Microsoft
Windows Server 2008 R2 Service Pack 1
N/A
Microsoft
Windows Server 2008 R2 Service Pack 1 (Server Core installation)
N/A
Microsoft
Windows Server 2012
N/A
Microsoft
Windows Server 2012 (Server Core installation)
N/A
Microsoft
Windows Server 2012 R2
N/A
Microsoft
Windows Server 2012 R2 (Server Core installation)
N/A

References

3 links

Record Details

Published
2013-12-11
Last updated
2026-10-08
Assigner (CNA)
microsoft
Credited to
-

More from Microsoft

All Microsoft CVEs→

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.