CVE-2016-0145 in the critical feed json
The font library in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold a…
published 2016-04-12 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-0183
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 40.8%
- EPSS 40.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
The font library in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; Windows 10 Gold and 1511; Office 2007 SP3 and 2010 SP2; Word Viewer; .NET Framework 3.0 SP2, 3.5, and 3.5.1; Skype for Business 2016; Lync 2010; Lync 2010 Attendee; Lync 2013 SP1; and Live Meeting 2007 Console allows remote attackers to execute arbitrary code via a crafted embedded font, aka "Graphics Memory Corruption Vulnerability."
Timeline
- Published
- First public exploit (EDB-39743)
Exploit prediction
40.84% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-39743 Microsoft Windows Kernel - 'win32k.sys' TTF Processing EBLC / EBSC Tables Pool Corruption (MS16-039) dos, 2016-04-28
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/39743/
exploit
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2016/ms16-039
vendor-advisory
-
securitytracker.com
/id/1035529
vdb-entry
-
securitytracker.com
/id/1035530
vdb-entry
-
securitytracker.com
/id/1035532
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1035528
vdb-entry
-
securitytracker.com
/id/1035531
vdb-entry
Sources
- CVE List CVE-2016-0145
- NVD CVE-2016-0145
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.