CVE-2016-3309

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-15), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2016-4341 (ENISA EUVD) · GHSA-7cmx-3w9q-4v5g (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 20%CVSS: 7.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

The kernel-mode drivers 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; and Windows 10 Gold, 1511, and 1607 allow local users to gain privileges via a crafted application, aka "Win32k Elevation of Privilege Vulnerability," a different vulnerability than CVE-2016-3308, CVE-2016-3310, and CVE-2016-3311.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
20%
EPSS %ILE
97th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
20% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2016-3309

Published

August 9, 2016

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Nov 16, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2016-3309
Web page🟡 PoC Available

Microsoft Windows 10 RS2 (x64) - 'win32kfull!bFill' Pool Overflow - Windows_x86-64 local Exploit

https://www.exploit-db.com/exploits/42960/
Web page

Microsoft Security Bulletin MS16-098 - Important | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-098
Web page

PSIRT.COM — Product Security Incident Response Team

http://www.securityfocus.com/bid/92297

Vendor Advisories for CVE-2016-3309(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 16× in last 7d / 82× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 1,907 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,807 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 03:11 UTCEchelonGraph re-scored
  2. 2026-11-22 03:11 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-11-21 05:25 UTCEchelonGraph re-scored
  4. 2026-11-21 05:25 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-11-20 16:28 UTCEPSS rescoreEPSS 20% · 97th percentile
  6. 2026-11-20 07:39 UTCEchelonGraph re-scored
  7. 2026-11-20 07:39 UTCVendor advisory
  8. 2026-11-20 07:39 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-11-19 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  10. 2026-11-19 09:53 UTCEchelonGraph re-scored
  11. 2026-11-19 09:53 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-11-18 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  13. 2026-11-18 12:07 UTCEchelonGraph re-scored
  14. 2026-11-18 12:07 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-11-17 14:19 UTCEchelonGraph re-scored
  16. 2026-11-17 14:19 UTCVendor advisory
  17. 2026-11-17 14:19 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-11-16 16:33 UTCVendor advisory
  19. 2026-11-16 16:33 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-11-15 18:39 UTCEchelonGraph re-scored
  21. 2026-11-15 18:39 UTCVendor advisory
  22. 2026-11-15 18:39 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-11-15 16:35 UTCEPSS rescoreEPSS 20% · 97th percentile
  24. 2026-11-14 20:54 UTCEchelonGraph re-scored
  25. 2026-11-14 20:54 UTCVendor advisory
Show 75 more
  1. 2026-11-14 20:54 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-11-14 16:30 UTCEPSS rescoreEPSS 20% · 97th percentile
  3. 2026-11-13 23:08 UTCEchelonGraph re-scored
  4. 2026-11-13 23:08 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-11-13 16:36 UTCEPSS rescoreEPSS 20% · 97th percentile
  6. 2026-11-13 01:22 UTCEchelonGraph re-scored
  7. 2026-11-13 01:22 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-11-12 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  9. 2026-11-12 03:36 UTCEchelonGraph re-scored
  10. 2026-11-12 03:36 UTCVendor advisory
  11. 2026-11-12 03:36 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-11-11 16:28 UTCEPSS rescoreEPSS 20% · 97th percentile
  13. 2026-11-11 05:50 UTCEchelonGraph re-scored
  14. 2026-11-11 05:50 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-11-10 16:30 UTCEPSS rescoreEPSS 20% · 97th percentile
  16. 2026-11-10 08:05 UTCEchelonGraph re-scored
  17. 2026-11-10 08:04 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-11-09 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  19. 2026-11-09 10:17 UTCEchelonGraph re-scored
  20. 2026-11-09 10:17 UTCVendor advisory
  21. 2026-11-09 10:17 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-11-08 16:29 UTCEPSS rescoreEPSS 20% · 97th percentile
  23. 2026-11-08 12:30 UTCEchelonGraph re-scored
  24. 2026-11-08 12:30 UTCVendor advisory
  25. 2026-11-08 12:30 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  26. 2026-11-07 16:29 UTCEPSS rescoreEPSS 20% · 97th percentile
  27. 2026-11-07 14:43 UTCVendor advisory
  28. 2026-11-07 14:43 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-11-06 16:58 UTCEchelonGraph re-scored
  30. 2026-11-06 16:58 UTCVendor advisory
  31. 2026-11-06 16:58 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  32. 2026-11-06 16:28 UTCEPSS rescoreEPSS 20% · 97th percentile
  33. 2026-11-05 19:13 UTCEchelonGraph re-scored
  34. 2026-11-05 19:13 UTCVendor advisory
  35. 2026-11-05 19:13 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  36. 2026-11-05 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  37. 2026-11-04 21:26 UTCEchelonGraph re-scored
  38. 2026-11-04 21:26 UTCVendor advisory
  39. 2026-11-04 21:26 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  40. 2026-11-04 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  41. 2026-11-03 23:41 UTCEchelonGraph re-scored
  42. 2026-11-03 23:41 UTCVendor advisory
  43. 2026-11-03 23:41 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-11-03 16:33 UTCEPSS rescoreEPSS 20% · 97th percentile
  45. 2026-11-03 01:55 UTCEchelonGraph re-scored
  46. 2026-11-03 01:55 UTCVendor advisory
  47. 2026-11-03 01:55 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-11-02 04:10 UTCEchelonGraph re-scored
  49. 2026-11-02 04:09 UTCVendor advisory
  50. 2026-11-02 04:09 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-11-01 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  52. 2026-11-01 06:20 UTCEchelonGraph re-scored
  53. 2026-11-01 06:20 UTCVendor advisory
  54. 2026-11-01 06:20 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-10-31 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  56. 2026-10-31 08:34 UTCEchelonGraph re-scored
  57. 2026-10-31 08:34 UTCVendor advisory
  58. 2026-10-31 08:34 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-10-30 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  60. 2026-10-30 10:49 UTCEchelonGraph re-scored
  61. 2026-10-30 10:49 UTCVendor advisory
  62. 2026-10-30 10:48 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-10-29 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  64. 2026-10-29 13:03 UTCEchelonGraph re-scored
  65. 2026-10-29 13:03 UTCVendor advisory
  66. 2026-10-29 13:03 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-10-28 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  68. 2026-10-28 15:17 UTCVendor advisory
  69. 2026-10-28 15:17 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-10-27 17:32 UTCEchelonGraph re-scored
  71. 2026-10-27 17:32 UTCVendor advisory
  72. 2026-10-27 17:32 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-10-27 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  74. 2026-10-26 19:46 UTCEchelonGraph re-scored
  75. 2026-10-26 19:46 UTCGHSA enrichmentGHSA-7cmx-3w9q-4v5g · GitHub severity HIGH · GitHub CVSS 7.8

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 Exploit-DB entry, 1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-42960
    Published Oct 6, 2017

    Microsoft Windows 10 RS2 (x64) - 'win32kfull!bFill' Pool Overflow

    Open source ↗
  • GitHub PoCsiberas/CVE-2016-3309_Reloaded
    Published Oct 6, 2017

    Exploits for the win32kfull!bFill vulnerability on Win10 x64 RS2 using Bitmap or Palette techniques

    Open source ↗

Frequently asked(6)

What is CVE-2016-3309?
CVE-2016-3309 is a critical-severity vulnerability; its CVE record was published on August 9, 2016. The kernel-mode drivers 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; and Windows 10 Gold, 1511, and 1607 allow local users to gain privileges via a crafted application, aka "Win32k Elevation of…
When was CVE-2016-3309 made public?
CVE-2016-3309 was made public on August 9, 2016: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on August 9, 2016. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2016-3309 actively exploited?
Yes. CISA added CVE-2016-3309 to the Known Exploited Vulnerabilities catalog on March 15, 2022, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2016-3309?
CVE-2016-3309 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2016-3309?
CVE-2016-3309 affects Microsoft Windows.
How do I remediate CVE-2016-3309?
A fix for CVE-2016-3309 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2016-3309 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-3309

Explore →

Is Your Infrastructure Affected by CVE-2016-3309?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.