How severe is CVE-2011-3402?

CVE-2011-3402 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2011-3402?

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

How do I patch CVE-2011-3402?

No patch has shipped for CVE-2011-3402 yet — track the microsoft windows 7 advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2011-3402 across my infrastructure?

Inventory every microsoft windows 7 deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2011-3402 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2011-3402?

O3 detects and blocks CVE-2011-3402 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2011-3402 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2011-3402, 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-2011-3402?

CVE-2011-3402 has an EPSS (Exploit Prediction Scoring System) score of 78.3%, 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-2011-3402 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2011-3402 (Microsoft Windows Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-10-06. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-10-27. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Which products and versions are affected by CVE-2011-3402?

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

Is there exploit tooling available for CVE-2011-3402?

A Metasploit module references CVE-2011-3402, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2011-3402 published, and has it been updated?

CVE-2011-3402 was published on November 4, 2011 and was last updated on June 16, 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 2025-10-06 — agencies required to remediate by 2025-10-27

CVE-2011-3402

HIGH

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,…

Published

Nov 4, 2011

Updated

Jun 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

78.3%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

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

Affected Products

5 products · 9 configurations

windows 7microsoft

all

windows server 2003microsoft

all

windows server 2008microsoft

all

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.

Unspecified vulnerability in the TrueType font parsing engine in win32k.…

github.comMetasploitSep 2020

Unspecified vulnerability in the TrueType font parsing engine in win32k.…

nvd.nist.govNVDSep 2020

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every microsoft windows 7 deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2011-3402 yet — track the microsoft windows 7 advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2011-3402 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2011-3402. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2011-3402 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2011-3402 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2011-3402

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2011-3402 being exploited in your environment?