How severe is CVE-2016-3235?

CVE-2016-3235 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-3235?

Affected package information for CVE-2016-3235 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2016-3235?

No fixed version has been published for CVE-2016-3235 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2016-3235 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2016-3235, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2016-3235?

CVE-2016-3235 has an EPSS (Exploit Prediction Scoring System) score of 81.2%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2016-3235 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2016-3235 (Microsoft Office OLE DLL Side Loading Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Which products and versions are affected by CVE-2016-3235?

CVE-2016-3235 affects microsoft visio (4 versions, e.g. 2007, 2010, 2013…); microsoft visio viewer (2 versions, e.g. 2007, 2010). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2016-3235 published, and has it been updated?

CVE-2016-3235 was published on June 16, 2016 and was last updated on April 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03

CVE-2016-3235

HIGH

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…

Published

Jun 16, 2016

Updated

Apr 22, 2026

Affected

0 pkgs

Patched

None yet

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

81.2%probability of exploitation in next 30 days

Very High Risk99th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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."

Affected Products

2 products · 6 configurations

Application

visiomicrosoft

4 versions

2007201020132016

Application

visio viewermicrosoft

2 versions

20072010

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-41706localwindows✓ Verified

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

by Metasploit · Dec 8, 2015

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-3235 in your stack?

O3 detects CVE-2016-3235 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works

CVSS Score

7.8/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Local

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction

Required

S:Scope

Unchanged

C:Confidentiality

High

I:Integrity

High

A:Availability

High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Weaponization

No known public exploit tooling found.

Timeline

First exploit

Dec 8, 2015

Disclosed

Jun 16, 2016

KEV added

Nov 3, 2021

Last updated

Apr 22, 2026

Identifiers

CVE-2016-3235

References

Advisorypacketstormsecurity.com Advisoryseclists.org Advisorysecurityfocus.com Advisorysecuritytracker.com Advisorypacketstormsecurity.com Advisoryseclists.org Advisorysecurityfocus.com Advisorysecuritytracker.com Fixdocs.microsoft.com Fixdocs.microsoft.com Exploit / PoCsecurify.nl Exploit / PoCsecurify.nl Webcisa.gov

Data from OSV.dev, enriched by O3 Security. Refreshed hourly.