Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2012-0151: WinVerifyTrust Signature Validation Vulnerability

Published Apr 10, 2012 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS87.7%100th percentile
CISA KEVYesAdded Jun 8, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2012-0151CWE-347

CVE-2012-0151 is a signature validation flaw in Microsoft Windows Authenticode handling. The vulnerability exists in the WinVerifyTrust/AuthentiCode signature verification logic on affected Windows versions because the digest of a signed portable executable file is not properly validated when additional content is appended. As a result, a specially modified PE file can retain an apparently valid digital signature even though attacker-controlled data has been added after signing. This weakness can be abused to make a tampered executable appear trustworthy to users or security controls that rely on Authenticode validation, enabling delivery of malicious content inside or alongside a signed file. The issue is user-assisted because successful exploitation depends on a target opening or executing the modified file.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can use a legitimately signed but modified PE file to bypass trust decisions based on Authenticode validation and induce execution of arbitrary code. The practical impact is defense evasion and initial compromise: malicious content can be concealed within a file that appears validly signed, increasing the likelihood of user execution and potentially reducing detection by controls that trust signed binaries. In campaigns abusing this weakness, the flaw has been used to hide script content in signed files and support malware delivery.

Mitigation

If you can’t patch tonight, do this now.

Where patching is not immediately possible, reduce reliance on Authenticode trust alone for execution decisions. Use application control, reputation-based protections, and content inspection capable of detecting appended or embedded malicious payloads in signed PE files. Restrict execution of untrusted files from user-writable locations, harden email and web download paths, and monitor for suspicious use of signed binaries as malware carriers. Additional strict signature validation settings may help detect related certificate-padding abuse, but that mitigation is primarily associated with later related issues and may not fully address this CVE by itself.

Remediation

Patch, then assume compromise.

Apply the Microsoft security updates that correct the WinVerifyTrust/AuthentiCode validation behavior for affected Windows versions. Systems running unsupported legacy Windows releases should be upgraded to supported versions that include the fix. Organizations should also review any workflows or security products that make allow/deny decisions solely on the presence of a valid Authenticode signature and ensure they validate file integrity beyond signature presence alone.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows Server 2003operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Vistaoperating_system
Microsoft CorporationWindows Xpoperating_system
FAQ

Frequently asked questions

Is CVE-2012-0151 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jun 8, 2022.
Is there a public exploit for CVE-2012-0151?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2012-0151.
Is there a patch for CVE-2012-0151?
Apply the Microsoft security updates that correct the WinVerifyTrust/AuthentiCode validation behavior for affected Windows versions. Systems running unsupported legacy Windows releases should be upgraded to supported versions that include the fix.
What products are affected by CVE-2012-0151?
Microsoft Corporation Windows 7, Microsoft Corporation Windows Server 2003, Microsoft Corporation Windows Server 2008, Microsoft Corporation Windows Vista, and Microsoft Corporation Windows Xp.
How severe is CVE-2012-0151?
CVE-2012-0151 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 87.7% (100th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.