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."
CVE-2016-3235
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.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
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 computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 98.6%
- KEV
- ⚠ Exploited
Published
June 16, 2016
Last Modified
April 22, 2026
Advisory Details (6)
Auto-updated May 19, 2026Full Disclosure: Microsoft Visio multiple DLL side loading vulnerabilities
http://seclists.org/fulldisclosure/2016/Jun/32Microsoft Visio multiple DLL side loading vulnerabilities
https://www.securify.nl/advisory/SFY20150804/microsoft_visio_multiple_dll_side_loading_vulnerabilities.htmlMicrosoft Security Bulletin MS16-070 - Critical | Microsoft Learn
https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-070All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 68× in last 7d / 361× 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 704 total refreshes for this CVE.
- 2026-07-23 14:14 UTCEPSS rescore
- 2026-07-23 01:22 UTCEG score recompute
- 2026-07-22 22:07 UTCVendor advisory
- 2026-07-22 22:07 UTCGHSA enrichment
- 2026-07-22 22:02 UTCEG score recompute
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 17:56 UTCEG score recompute
- 2026-07-22 17:55 UTCGHSA enrichment
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-22 13:43 UTCGHSA enrichment
- 2026-07-22 09:31 UTCVendor advisory
- 2026-07-22 09:31 UTCGHSA enrichment
- 2026-07-22 05:20 UTCVendor advisory
- 2026-07-22 05:20 UTCGHSA enrichment
- 2026-07-22 01:05 UTCVendor advisory
- 2026-07-22 01:05 UTCGHSA enrichment
- 2026-07-21 18:46 UTCEG score recompute
- 2026-07-21 18:46 UTCVendor advisory
- 2026-07-21 18:45 UTCGHSA enrichment
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 14:33 UTCVendor advisory
- 2026-07-21 14:33 UTCGHSA enrichment
- 2026-07-21 10:22 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-21 10:22 UTCGHSA enrichment
- 2026-07-21 06:10 UTCVendor advisory
- 2026-07-21 06:10 UTCGHSA enrichment
- 2026-07-21 01:59 UTCVendor advisory
- 2026-07-21 01:59 UTCGHSA enrichment
- 2026-07-20 21:48 UTCVendor advisory
- 2026-07-20 21:48 UTCGHSA enrichment
- 2026-07-20 17:37 UTCEG score recompute
- 2026-07-20 17:37 UTCVendor advisory
- 2026-07-20 17:37 UTCGHSA enrichment
- 2026-07-20 17:03 UTCEPSS rescore
- 2026-07-20 13:26 UTCGHSA enrichment
- 2026-07-20 09:15 UTCVendor advisory
- 2026-07-20 09:15 UTCGHSA enrichment
- 2026-07-20 05:04 UTCVendor advisory
- 2026-07-20 05:04 UTCGHSA enrichment
- 2026-07-20 00:52 UTCVendor advisory
- 2026-07-20 00:52 UTCGHSA enrichment
- 2026-07-19 20:41 UTCVendor advisory
- 2026-07-19 20:41 UTCGHSA enrichment
- 2026-07-19 16:29 UTCEG score recompute
- 2026-07-19 16:29 UTCVendor advisory
- 2026-07-19 16:29 UTCGHSA enrichment
- 2026-07-19 14:27 UTCEPSS rescore
- 2026-07-19 12:17 UTCVendor advisory
- 2026-07-19 12:17 UTCGHSA enrichment
- 2026-07-19 08:01 UTCVendor advisory
- 2026-07-19 08:01 UTCGHSA enrichment
- 2026-07-19 03:50 UTCEG score recompute
- 2026-07-19 03:50 UTCVendor advisory
- 2026-07-19 03:49 UTCGHSA enrichment
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-18 23:37 UTCGHSA enrichment
- 2026-07-18 19:27 UTCVendor advisory
- 2026-07-18 19:27 UTCGHSA enrichment
- 2026-07-18 15:16 UTCVendor advisory
- 2026-07-18 15:16 UTCGHSA enrichment
- 2026-07-18 11:05 UTCEG score recompute
- 2026-07-18 11:05 UTCVendor advisory
- 2026-07-18 11:05 UTCGHSA enrichment
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-18 06:53 UTCVendor advisory
- 2026-07-18 06:53 UTCGHSA enrichment
- 2026-07-18 02:42 UTCVendor advisory
- 2026-07-18 02:41 UTCGHSA enrichment
- 2026-07-17 22:30 UTCVendor advisory
- 2026-07-17 22:30 UTCGHSA enrichment
- 2026-07-17 18:19 UTCVendor advisory
- 2026-07-17 18:19 UTCGHSA enrichment
- 2026-07-17 14:08 UTCVendor advisory
- 2026-07-17 14:08 UTCGHSA enrichment
- 2026-07-17 09:57 UTCEG score recompute
- 2026-07-17 09:57 UTCVendor advisory
- 2026-07-17 09:57 UTCGHSA enrichment
- 2026-07-17 05:46 UTCVendor advisory
- 2026-07-17 05:46 UTCGHSA enrichment
- 2026-07-17 01:35 UTCVendor advisory
- 2026-07-17 01:34 UTCGHSA enrichment
- 2026-07-16 21:23 UTCVendor advisory
- 2026-07-16 21:23 UTCGHSA enrichment
- 2026-07-16 17:12 UTCVendor advisory
- 2026-07-16 17:12 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 13:00 UTCVendor advisory
- 2026-07-16 13:00 UTCGHSA enrichment
- 2026-07-16 08:48 UTCVendor advisory
- 2026-07-16 08:48 UTCGHSA enrichment
- 2026-07-16 04:37 UTCVendor advisory
- 2026-07-16 04:37 UTCGHSA enrichment
- 2026-07-16 00:26 UTCVendor advisory
- 2026-07-16 00:26 UTCGHSA enrichment
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✓ verifiedFirst 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✓ verifiedFirst seen Dec 8, 2015
Office OLE Multiple DLL Side Loading Vulnerabilities
Open source ↗
Frequently asked(6)
What is CVE-2016-3235?
When was CVE-2016-3235 disclosed?
Is CVE-2016-3235 actively exploited?
What is the CVSS score of CVE-2016-3235?
Which products are affected by CVE-2016-3235?
How do I remediate CVE-2016-3235?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2016-3235
Is Your Infrastructure Affected by CVE-2016-3235?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.