FalehSec Exploited-vulnerability triage · joined from CISA KEV, NVD CVSS and EPSS

CVE-2011-3402

Microsoft · Windows · Microsoft Windows Remote Code Execution Vulnerability

Verdict
Patch first · actively exploited, reachable from the internet without credentials, and in the top 1% of CVEs by near-term exploitation probability

Added to CISA KEV 2025-10-06 · exploited in the wild for 356 days

What an attacker can reach How likely Time What CISA says to do Sources All 545

What an attacker can reach

CVSS 8.8 HIGH. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.

Attack vectornetworkreachable over the network, with no local access needed
Privileges requirednoneneeds no credentials at all
User interactionrequiredneeds a user to click, load or submit something first
Base vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

This describes the vulnerability. It says nothing about whether your systems run it.

How likely

EPSS puts the probability of exploitation in the next 30 days at 0.7814, which places it in the top 1% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.

EPSS probability0.7814
Percentile0.996 — top 1%

Time

Added to KEV2025-10-06
Days exploited356
Federal remediation duenot set
Ransomware useno known ransomware campaign use

What CISA says to do

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Unspecified vulnerability in the TrueType font parsing engine in win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, and Windows 7 Gold and SP1 allows remote attackers to execute arbitrary code via crafted font data in a Word document or web page, as exploited in the wild in November 2011 by Duqu, aka "TrueType Font Parsing Vulnerability."

Sources