Public proof of concept

CVE-2016-3209

A public proof of concept exists; no exploitation attested.

Published2016-10-14
WeaknessCWE-200

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Graphics Device Interface (aka GDI or GDI+) 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, 1511, and 1607; Office 2007 SP3; Office 2010 SP2; Word Viewer; Skype for Business 2016; Lync 2013 SP1; Lync 2010; Lync 2010 Attendee; Live Meeting 2007 Console; .NET Framework 3.0 SP2, 3.5, 3.5.1, 4.5.2, and 4.6; and Silverlight 5 allows remote attackers to bypass the ASLR protection mechanism via unspecified vectors, aka "True Type Font Parsing Information Disclosure Vulnerability."

Timeline

dates in UTC

2016-10-1402:59CVE publishedNVD
2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-3209?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-3209?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Microsoft .net framework

Branch	Affected	Fixed in	Source
3.0	= 3.0	no fix published	NVD
3.5	= 3.5	no fix published	NVD
3.5	= 3.5.1	no fix published	NVD
4.5	= 4.5.2	no fix published	NVD
4.6	= 4.6	no fix published	NVD

Microsoft windows 10

Branch	Affected	Fixed in	Source
—	all versions	no fix published	NVD
1511.x	= 1511	no fix published	NVD
1607.x	= 1607	no fix published	NVD

Microsoft lync

Branch	Affected	Fixed in	Source
2010.x	= 2010	no fix published	NVD
2013.x	= 2013	no fix published	NVD

11 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

No fix published by the sources we read yet. NVD record

Detection

read 2026-10-23 19:23 UTC

Nuclei template: none so far
Exploit-DB: EDB-40598
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.05.5read 2026-10-23
NVDCVSS 2.05read 2026-10-23
NVDweakness (CWE)CWE-200read 2026-10-23
FIRST EPSSEPSS score53.7 %read 2026-10-23
Exploit-DBdetectionread 2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Published: 2016-10-14
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2016-3209?

Is CVE-2016-3209 actively exploited?

Active exploitation of CVE-2016-3209 has not been confirmed. Its EPSS score was 53.7% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2016-3209?

CVE-2016-3209 has a CVSS v3 base score of 5.5 (MEDIUM severity), with vector string CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database