Microsoft Windows 10
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
Timeline
Days relative to CVE publicationNo public PoC found yet; added to CISA KEV 8.1 years after publication.
PoC repositories
Found on GitHub.2 pending · 13 informational · 1 not a PoC · 3 suspicious or fake
Pending 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| ptrstr/MsiAuthenticodeInject | 14 Jun 2023 +9.5 y | 0 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| Live-Hack-CVE/CVE-2013-3900 | unknown | 0 | Pending · repository unavailable (HTTP 404) |
Informational 13
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| snoopopsec/vulnerability-CVE-2013-3900 | 6 Sep 2022 +8.7 y | 0 | Informational · detection |
| CyberCondor/Fix-WinVerifyTrustSignatureValidationVuln | 3 Jul 2023 +9.6 y | 3 | Informational · detection
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| Securenetology/CVE-2013-3900 | 21 May 2024 +10.4 y | 0 | Informational · detection
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| AdenilsonSantos/WinVerifyTrust | 23 Feb 2025 +11.2 y | 0 | Informational · detection |
| DavidBr27/CVE-2013-3900-Remediation-Script | 16 Mar 2025 +11.3 y | 0 | Informational · detection |
| piranhap/CVE-2013-3900_Remediation_PowerShell | 31 Mar 2025 +11.3 y | 0 | Informational · detection
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| pkblanks/Remediating-CVE-2013-3900-EnableCertPaddingCheck- | 12 Jul 2025 +11.6 y | 1 | Informational · write-up |
| malaya-m/cve-2013-3900-remediation-report | 16 Jul 2025 +11.6 y | 0 | Informational · detection |
| Sabecomoeh/CVE-2013-3900 | 4 Aug 2025 +11.6 y | 0 | Informational · detection
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| oukridrig772/-WinVerifyTrust-Signature-Validation-CVE-2013-3900-Mitigation | 6 Sep 2025 +11.7 y | 0 | Informational · detection
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
| ksgassama-lab/vulnerability-remediation-cve-2013-3900 | 16 Jan 2026 +12.1 y | 0 | Informational · detection
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| SDimitri05/cve-2013-3900-winverifytrust-mitigation | 11 Feb 2026 +12.2 y | 0 | Informational · detection
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| kingsrule50/nessus-vulnerability-scanning-lab | 19 Jul 2026 +12.6 y | 0 | Informational · detection |
Not a PoC 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| OtisSymbos/CVE-2013-3900-WinTrustVerify | 11 Sep 2024 +10.8 y | 1 | Not a PoC · unrelated
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Suspicious or fake 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| jason-klein/signed-nsis-exe-append-payload | 26 Mar 2018 +4.3 y | 24 | Suspicious · score 75
Why suspicious
|
| PREN0MEN/CVE-2013-3900-PowerShell-PoC | 18 Aug 2025 +11.7 y | 5 | Fake |
| norvethil/CVE-2013-3900-PowerShell-PoC | 18 Aug 2025 +11.7 y | 5 | Suspicious · score 50
Why suspicious
|
Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.