How severe is CVE-2014-4113?

CVE-2014-4113 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2014-4113?

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

How do I patch CVE-2014-4113?

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

How do I detect CVE-2014-4113 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 exploitation 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-2014-4113 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-2014-4113?

O3 detects and blocks CVE-2014-4113 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-2014-4113 actively exploited in the wild?

Yes. There are 20 known exploit references for CVE-2014-4113, including 6 documented proof-of-concept exploits on Exploit-DB and 11 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-2014-4113?

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

Yes. CVE-2014-4113 (Microsoft Win32k Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-05-04. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-25. The required action was: Apply updates per vendor instructions. 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-2014-4113?

CVE-2014-4113 affects microsoft windows 7; microsoft windows 8; microsoft windows 8.1; microsoft windows rt, and 5 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2014-4113 published, and has it been updated?

CVE-2014-4113 was published on October 15, 2014 and was last updated on June 17, 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 2022-05-04 — agencies required to remediate by 2022-05-25

CVE-2014-4113

HIGH

win32k.sys in the kernel-mode drivers in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server…

Published

Oct 15, 2014

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

20 known

EPSS Exploitation Probability

via FIRST.org ↗

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

win32k.sys in the kernel-mode drivers in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allows local users to gain privileges via a crafted application, as exploited in the wild in October 2014, aka "Win32k.sys Elevation of Privilege Vulnerability."

Affected Products

9 products · 11 configurations

windows 7microsoft

all

windows 8microsoft

all

windows 8.1microsoft

all

windows rtmicrosoft

all

windows rt 8.1microsoft

all

windows server 2003microsoft

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.

EDB-39666localwindows

Microsoft Windows Kernel - 'win32k.sys' Local Privilege Escalation (MS14-058)

by MWR InfoSecurity · Apr 5, 2016

Exploit-DB Source

EDB-35101localwindows✓ Verified

Microsoft Windows - TrackPopupMenu Win32k Null Pointer Dereference (MS14-058) (Metasploit)

by Metasploit · Oct 28, 2014

Exploit-DB Source

EDB-37064localwindows_x86-64✓ Verified

Microsoft Windows 8.0/8.1 (x64) - 'TrackPopupMenu' Local Privilege Escalation (MS14-058)

by ryujin · May 19, 2015

Exploit-DB Source

EDB-46945localwindows

Microsoft Windows 8.1/ Server 2012 - 'Win32k.sys' Local Privilege Escalation (MS14-058)

by anonymous · Nov 24, 2014

Exploit-DB Source

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 exploitation 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-2014-4113 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-2014-4113 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-2014-4113. 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-2014-4113 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2014-4113 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-2014-4113

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-2014-4113 being exploited in your environment?