Exploited CVEs / Microsoft / CVE-2012-0151
CVE-2012-0151
Microsoft Windows Authenticode Signature Verification Remote Code Execution Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-06-22 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Microsoft Security Update Guide (MSRC), linked below.
Actively exploited Microsoft Windows vulnerability. Added to the CISA KEV catalog 2022-06-08.
Risk summary
Updated July 25, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2012-0151
This flaw lets an attacker modify a signed Windows executable so that WinVerifyTrust still treats it as validly signed, meaning tampered code can slip past Authenticode signature checks that users and software rely on to trust binaries. Because it requires the victim to run or open a crafted file, phishing and drive-by delivery are the realistic paths, and CISA confirmed active exploitation when it added this to the KEV catalog in 2022. Severity is rated High, and any Windows system still lacking the relevant Microsoft update remains exposed even though signatures on affected files appear legitimate.
Do this: Apply the Microsoft Windows update that corrects Authenticode signature validation to all affected systems and confirm it is present across your fleet.
AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2012-0151
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2012-0151
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA required action
Federal (BOD 22-01) remediation due date: 2022-06-22 (past due).
Official fix for CVE-2012-0151
The authoritative fix and affected-version list are published by the vendor. Find the Windows advisory on Microsoft Security Update Guide (MSRC).
Common questions about CVE-2012-0151
Is CVE-2012-0151 actively exploited?
Yes. CVE-2012-0151 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2022-06-08, which means exploitation in the wild has been confirmed, not predicted.
What is the CISA deadline and required action for CVE-2012-0151?
CISA set the federal (BOD 22-01) remediation due date at 2022-06-22, which has passed; treat any unremediated system as overdue.
What fixes CVE-2012-0151?
The authoritative fix is in the vendor advisory: see Microsoft Security Update Guide (MSRC) for the patched Windows versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2012-0151?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2012-0151's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).
More exploited Microsoft CVEs
The newest Microsoft entries on the CISA KEV catalog:
All Microsoft exploited CVEs on one page: Microsoft vulnerabilities actively exploited.
Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.
