win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 does not properly validate addresses, which a…

published 2013-12-11 12y ago modified 2026-06-16 4mo ago also EUVD-2013-3831

cvss: 7.2; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.3%; EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits: 0; none known

win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 does not properly validate addresses, which allows local users to gain privileges via a crafted application, aka "Win32k Memory Corruption Vulnerability."

Is CVE-2013-3899 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.26% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	7.2	AV:L/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-20 Improper Input Validation

References

docs.microsoft.com /en-us/security-updates/securitybulletins/2013/ms13-101
vendor-advisory

Sources

CVE List CVE-2013-3899
NVD CVE-2013-3899

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.