How severe is CVE-2012-0151?

CVE-2012-0151 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2012-0151?

Affected package information for CVE-2012-0151 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2012-0151?

No fixed version has been published for CVE-2012-0151 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2012-0151 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2012-0151, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2012-0151?

CVE-2012-0151 has an EPSS (Exploit Prediction Scoring System) score of 89.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2012-0151 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2012-0151 (Microsoft Windows Authenticode Signature Verification Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-06-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-06-22. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2012-0151?

CVE-2012-0151 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2012-0151?

CVE-2012-0151 affects microsoft windows 7; microsoft windows server 2003; microsoft windows server 2008 (1 version, e.g. r2); microsoft windows vista, and 1 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2012-0151 published, and has it been updated?

CVE-2012-0151 was published on April 10, 2012 and was last updated on April 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-06-08 — agencies required to remediate by 2022-06-22

CVE-2012-0151

HIGH

The Authenticode Signature Verification function in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, Windows 7…

Published

Apr 10, 2012

Updated

Apr 22, 2026

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

89.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

The Authenticode Signature Verification function in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, Windows 7 Gold and SP1, and Windows 8 Consumer Preview does not properly validate the digest of a signed portable executable (PE) file, which allows user-assisted remote attackers to execute arbitrary code via a modified file with additional content, aka "WinVerifyTrust Signature Validation Vulnerability."

Affected Products

5 products · 18 configurations

windows 7microsoft

all

windows server 2003microsoft

all

windows server 2008microsoft

1 version

windows vistamicrosoft

all

windows xpmicrosoft

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The Authenticode Signature Verification function in Microsoft Windows XP…

cisa.govCISAJun 2022

The Authenticode Signature Verification function in Microsoft Windows XP…

research.checkpoint.comAPINov 2021

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-0151 in your stack?

O3 detects CVE-2012-0151 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works

CVSS Score

7.8/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Local

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction

Required

S:Scope

Unchanged

C:Confidentiality

High

I:Integrity

High

A:Availability

High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CWE Classification

CWE-20Improper Input Validation

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Apr 10, 2012

KEV added

Jun 8, 2022

First exploit

Jun 8, 2022

Last updated

Apr 22, 2026

Identifiers

CVE-2012-0151

References

Advisorysecuritytracker.com Advisoryus-cert.gov Advisorysecuritytracker.com Advisoryus-cert.gov Fixdocs.microsoft.com Fixdocs.microsoft.com Webosvdb.org Websecunia.com Weboval.cisecurity.org Webosvdb.org Websecunia.com Weboval.cisecurity.org Webcisa.gov

Data from OSV.dev, enriched by O3 Security. Refreshed hourly.