basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2011-3402
CVE-2011-3402 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Microsoft Windows vulnerability

Microsoft Windows kernel TrueType font parsing vulnerability in win32k.sys allows remote code execution through malicious font data embedded in documents or web pages.

Verdict

Today item — known-exploited.

Remote attackers can achieve arbitrary code execution by crafting malicious TrueType font data delivered via Word documents or web content, exploiting a parsing flaw in the Windows kernel-mode font engine.

CISA KEV Yes · 2025-10-063EPSS 0.78285 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
10 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-10-06).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.78285 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious TrueType font and embed it in a Word document or host it on a web page.
Business
An employee or user downloads and opens the document or visits the compromised web page.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I trigger the vulnerable font parsing code in win32k.sys when the system processes the malicious font data.
Business
The kernel-mode driver processes untrusted font input without proper validation.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code with kernel privileges on the target system.
Business
The attacker gains complete system compromise, enabling data theft, malware installation, or lateral movement.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 10 reported-exploitation source(s)
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.