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

Affected: Windows 7 (Microsoft); Windows Server 2003 (Microsoft); Windows Server 2008 (Microsoft) versions r2, r2-sp1, among others. The full list is in the CVE brief.

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

It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Nov 15, 2021.

Is CVE-2012-0151 in the CISA KEV catalog?

Yes. It was added on Jun 8, 2022 with a federal remediation due date of Jun 22, 2022.

Is there a public exploit for CVE-2012-0151?

Public exploit code is available.

Is there a fix for CVE-2012-0151?

No fixed version is listed yet; check the vendor advisory for mitigations.

How urgently should CVE-2012-0151 be patched?

Brandefense priority: patch immediately, because it is listed as exploited in the wild.

Request A Demo

Vulnerability Intelligence

CVE-2012-0151

HighExploitedPublic exploit

Published Apr 10, 2012 · Updated Apr 22, 2026

Key Facts

Patch immediately

CVE-2012-0151 is a high-severity vulnerability (CVSS 7.8 v3.1) affecting Windows 7 (Microsoft), Windows Server 2003 (Microsoft), Windows Server 2008 (Microsoft) and 2 more products.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Nov 15, 2021. Public exploit code is available.
EPSS estimates a 88% probability of exploitation in the next 30 days.
No fixed version is listed yet; check the vendor advisory for mitigations.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.

CVSS v3.1

7.8

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

EPSS (30-day exploit likelihood)

88%

Higher than 99.7% of all scored CVEs

Exploited in the wild

Yes

4 catalog listings

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2012-0151 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

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."

Known-Exploited Catalog Listings

Catalog	Added	Remediation due	Ransomware use
CISA KEV	Jun 8, 2022	Jun 22, 2022	Not reported
Industry KEV feed	Nov 15, 2021	Jun 22, 2022	Not reported
CIRCL KEV	Jun 8, 2022	Jun 22, 2022	Not reported
ENISA EUVD	Jun 8, 2022	n/a	Not reported

Required action: Apply updates per vendor instructions.

Affected Products

15 affected entries in total

Product	Affected versions	Fixed in
Windows 7Microsoft	See advisory	n/a
Windows Server 2003Microsoft	See advisory	n/a
Windows Server 2008Microsoft	r2, r2-sp1	n/a
Windows VistaMicrosoft	See advisory	n/a
Windows XpMicrosoft	See advisory	n/a

Timeline

Publicly disclosed
Apr 10, 2012
Added to Industry KEV feed
Nov 15, 2021
Added to CISA KEV
Jun 8, 2022
Added to CIRCL KEV
Jun 8, 2022
Added to ENISA EUVD
Jun 8, 2022
Last updated
Apr 22, 2026

Weakness Type

CWE-20 Improper Input Validation

References

4 more references in the full CVE brief

FAQ

Common Questions.

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…
Affected: Windows 7 (Microsoft); Windows Server 2003 (Microsoft); Windows Server 2008 (Microsoft) versions r2, r2-sp1, among others. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Nov 15, 2021.
Yes. It was added on Jun 8, 2022 with a federal remediation due date of Jun 22, 2022.
Public exploit code is available.
No fixed version is listed yet; check the vendor advisory for mitigations.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.

Is CVE-2012-0151 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.