CVE-2016-3235

CRITICALNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 43%CVSS: 7.8Exploit: cisa kev · ssvc active · Metasploit · Exploit-DB (verified) · epss top5pct · public exploitExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Microsoft Visio 2007 SP3, Visio 2010 SP2, Visio 2013 SP1, Visio 2016, Visio Viewer 2007 SP3, and Visio Viewer 2010 mishandle library loading, which allows local users to gain privileges via a crafted application, aka "Microsoft Office OLE DLL Side Loading Vulnerability."

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact, and watch the vendor's advisory for the fix.
EPSS PROB
43%
EPSS %ILE
98th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact, and watch the vendor's advisory for the fix.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 16, 2016

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated May 19, 2026
No patch confirmed yet.
generic
http://www.securitytracker.com/id/1036093
generic
http://www.securityfocus.com/archive/1/538685/100/0/threaded
generic

Full Disclosure: Microsoft Visio multiple DLL side loading vulnerabilities

http://seclists.org/fulldisclosure/2016/Jun/32
generic

Packet Storm

http://packetstormsecurity.com/files/137490/Microsoft-Visio-DLL-Hijacking.html
generic

Microsoft Visio multiple DLL side loading vulnerabilities

https://www.securify.nl/advisory/SFY20150804/microsoft_visio_multiple_dll_side_loading_vulnerabilities.html
generic

Microsoft Security Bulletin MS16-070 - Critical | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-070

Vendor Advisories for CVE-2016-3235(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 90× in last 7d / 389× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 1,605 total refreshes for this CVE.

  1. 2026-10-04 11:20 UTCVendor advisory
  2. 2026-10-04 11:20 UTCGHSA enrichment
  3. 2026-10-04 07:09 UTCVendor advisory
  4. 2026-10-04 07:09 UTCGHSA enrichment
  5. 2026-10-04 02:59 UTCVendor advisory
  6. 2026-10-04 02:58 UTCGHSA enrichment
  7. 2026-10-03 22:48 UTCVendor advisory
  8. 2026-10-03 22:48 UTCGHSA enrichment
  9. 2026-10-03 18:37 UTCVendor advisory
  10. 2026-10-03 18:37 UTCGHSA enrichment
  11. 2026-10-03 14:25 UTCEG score recompute
  12. 2026-10-03 14:25 UTCVendor advisory
  13. 2026-10-03 14:24 UTCGHSA enrichment
  14. 2026-10-03 14:21 UTCEPSS rescore
  15. 2026-10-03 10:13 UTCVendor advisory
  16. 2026-10-03 10:13 UTCGHSA enrichment
  17. 2026-10-03 06:02 UTCVendor advisory
  18. 2026-10-03 06:02 UTCGHSA enrichment
  19. 2026-10-03 01:51 UTCVendor advisory
  20. 2026-10-03 01:51 UTCGHSA enrichment
  21. 2026-10-02 21:40 UTCVendor advisory
  22. 2026-10-02 21:40 UTCGHSA enrichment
  23. 2026-10-02 17:29 UTCEG score recompute
  24. 2026-10-02 17:29 UTCVendor advisory
  25. 2026-10-02 17:29 UTCGHSA enrichment
Show 75 more
  1. 2026-10-02 13:19 UTCVendor advisory
  2. 2026-10-02 13:19 UTCGHSA enrichment
  3. 2026-10-02 09:08 UTCVendor advisory
  4. 2026-10-02 09:08 UTCGHSA enrichment
  5. 2026-10-02 04:58 UTCVendor advisory
  6. 2026-10-02 04:58 UTCGHSA enrichment
  7. 2026-10-02 00:46 UTCVendor advisory
  8. 2026-10-02 00:46 UTCGHSA enrichment
  9. 2026-10-01 20:32 UTCEG score recompute
  10. 2026-10-01 20:32 UTCVendor advisory
  11. 2026-10-01 20:32 UTCGHSA enrichment
  12. 2026-10-01 19:43 UTCEPSS rescore
  13. 2026-10-01 16:21 UTCVendor advisory
  14. 2026-10-01 16:21 UTCGHSA enrichment
  15. 2026-10-01 12:10 UTCVendor advisory
  16. 2026-10-01 12:10 UTCGHSA enrichment
  17. 2026-10-01 07:59 UTCVendor advisory
  18. 2026-10-01 07:59 UTCGHSA enrichment
  19. 2026-10-01 03:48 UTCVendor advisory
  20. 2026-10-01 03:48 UTCGHSA enrichment
  21. 2026-09-30 23:38 UTCVendor advisory
  22. 2026-09-30 23:38 UTCGHSA enrichment
  23. 2026-09-30 19:26 UTCGHSA enrichment
  24. 2026-09-30 15:15 UTCEG score recompute
  25. 2026-09-30 15:15 UTCVendor advisory
  26. 2026-09-30 15:15 UTCGHSA enrichment
  27. 2026-09-30 14:58 UTCEPSS rescore
  28. 2026-09-30 11:04 UTCVendor advisory
  29. 2026-09-30 11:04 UTCGHSA enrichment
  30. 2026-09-30 06:53 UTCVendor advisory
  31. 2026-09-30 06:53 UTCGHSA enrichment
  32. 2026-09-30 02:42 UTCVendor advisory
  33. 2026-09-30 02:42 UTCGHSA enrichment
  34. 2026-09-29 22:32 UTCVendor advisory
  35. 2026-09-29 22:31 UTCGHSA enrichment
  36. 2026-09-29 18:18 UTCVendor advisory
  37. 2026-09-29 18:18 UTCGHSA enrichment
  38. 2026-09-29 14:07 UTCVendor advisory
  39. 2026-09-29 14:07 UTCGHSA enrichment
  40. 2026-09-29 09:56 UTCVendor advisory
  41. 2026-09-29 09:56 UTCGHSA enrichment
  42. 2026-09-29 05:46 UTCVendor advisory
  43. 2026-09-29 05:46 UTCGHSA enrichment
  44. 2026-09-29 01:35 UTCEG score recompute
  45. 2026-09-29 01:35 UTCVendor advisory
  46. 2026-09-29 01:35 UTCGHSA enrichment
  47. 2026-09-28 21:25 UTCVendor advisory
  48. 2026-09-28 21:25 UTCGHSA enrichment
  49. 2026-09-28 17:14 UTCVendor advisory
  50. 2026-09-28 17:13 UTCGHSA enrichment
  51. 2026-09-28 13:01 UTCVendor advisory
  52. 2026-09-28 13:01 UTCGHSA enrichment
  53. 2026-09-28 08:50 UTCVendor advisory
  54. 2026-09-28 08:50 UTCGHSA enrichment
  55. 2026-09-28 04:40 UTCVendor advisory
  56. 2026-09-28 04:40 UTCGHSA enrichment
  57. 2026-09-28 00:29 UTCVendor advisory
  58. 2026-09-28 00:29 UTCGHSA enrichment
  59. 2026-09-27 21:51 UTCCISA KEV update
  60. 2026-09-27 20:18 UTCVendor advisory
  61. 2026-09-27 20:18 UTCGHSA enrichment
  62. 2026-09-27 16:07 UTCEG score recompute
  63. 2026-09-27 16:07 UTCVendor advisory
  64. 2026-09-27 16:07 UTCGHSA enrichment
  65. 2026-09-27 13:40 UTCEPSS rescore
  66. 2026-09-27 11:57 UTCVendor advisory
  67. 2026-09-27 11:57 UTCGHSA enrichment
  68. 2026-09-27 07:47 UTCVendor advisory
  69. 2026-09-27 07:47 UTCGHSA enrichment
  70. 2026-09-27 03:36 UTCVendor advisory
  71. 2026-09-27 03:35 UTCGHSA enrichment
  72. 2026-09-26 23:23 UTCVendor advisory
  73. 2026-09-26 23:22 UTCGHSA enrichment
  74. 2026-09-26 19:09 UTCEG score recompute
  75. 2026-09-26 19:09 UTCVendor advisory

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-41706✓ verified
    First seen Dec 8, 2015

    Microsoft Office - OLE Multiple DLL Side Loading Vulnerabilities (MS15-132/MS16-014/MS16-025/MS16-041/MS16-070) (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/fileformat/office_ole_multiple_dll_hijack✓ verified
    First seen Dec 8, 2015

    Office OLE Multiple DLL Side Loading Vulnerabilities

    Open source ↗

Frequently asked(6)

What is CVE-2016-3235?
CVE-2016-3235 is a critical vulnerability published on June 16, 2016. Microsoft Visio 2007 SP3, Visio 2010 SP2, Visio 2013 SP1, Visio 2016, Visio Viewer 2007 SP3, and Visio Viewer 2010 mishandle library loading, which allows local users to gain privileges via a crafted application, aka "Microsoft Office OLE DLL Side Loading Vulnerability."
When was CVE-2016-3235 disclosed?
CVE-2016-3235 was first published on June 16, 2016, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-3235 actively exploited?
Yes. CISA added CVE-2016-3235 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Office. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2016-3235?
CVE-2016-3235 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-3235?
CVE-2016-3235 affects Microsoft Office.
How do I remediate CVE-2016-3235?
No fix for CVE-2016-3235 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2016-3235 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2016-3235?

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

Book a Demo →Browse All CVEs