Visio Viewer vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited4 versions
The short answer

Visio Viewer is made by Microsoft. We track 9 published vulnerabilities in it, across 4 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 3 November 2021. If you run Visio Viewer, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Visio Viewer flaw added to the known-exploited list is CVE-2016-3235, on 3 November 2021. We keep watching the known-exploited list.

Versions

Which versions of Visio Viewer do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2016-3235Exploited list, 3 Nov 2021

    Microsoft Office OLE DLL Side Loading Vulnerability

    2007-sp32010
Known exploited

Which Visio Viewer vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.8
    CVE-2016-3235HighKnown exploited
    Microsoft Office OLE DLL Side Loading Vulnerability

    Microsoft Office Object Linking & Embedding (OLE) dynamic link library (DLL) contains a side loading vulnerability due to it improperly validating input before loading libraries.

    Chance of use43%Known exploited since3 Nov 2021
Exploit likelihood

Which Visio Viewer flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 43%
    CVE-2016-3235HighKnown exploited

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

    CVSS7.8Published16 Jun 2016
  2. 27%

    Microsoft Visio Viewer 2010 SP1 allows remote attackers to execute arbitrary code via a crafted Visio file that triggers incorrect memory allocation, aka "Visio Viewer Tree Object Type Confusion Vulnerability."

    CVSS9.3Published13 Mar 2013
  3. 25%

    Microsoft Visio Viewer 2010 Gold and SP1 does not properly validate attributes in Visio files, which allows remote attackers to execute arbitrary code via a crafted file, aka "VSD File Format Memory Corruption...

    CVSS9.3Published9 May 2012
  4. 24%

    Buffer overflow in Microsoft Visio 2010 SP1 and Visio Viewer 2010 SP1 allows remote attackers to execute arbitrary code via a crafted Visio file, aka "Visio DXF File Format Buffer Overflow Vulnerability."

    CVSS9.3Published15 Aug 2012
  5. 20%

    Microsoft Visio Viewer 2010 Gold and SP1 does not properly handle memory during the parsing of files, which allows remote attackers to execute arbitrary code via crafted attributes in a Visio file, aka "VSD File...

    CVSS9.3Published14 Feb 2012
  6. 20%

    Microsoft Visio Viewer 2010 Gold and SP1 does not properly handle memory during the parsing of files, which allows remote attackers to execute arbitrary code via crafted attributes in a Visio file, aka "VSD File...

    CVSS9.3Published14 Feb 2012
  7. 20%

    Microsoft Visio Viewer 2010 Gold and SP1 does not properly handle memory during the parsing of files, which allows remote attackers to execute arbitrary code via crafted attributes in a Visio file, aka "VSD File...

    CVSS9.3Published14 Feb 2012
  8. 20%

    Microsoft Visio Viewer 2010 Gold and SP1 does not properly handle memory during the parsing of files, which allows remote attackers to execute arbitrary code via crafted attributes in a Visio file, aka "VSD File...

    CVSS9.3Published14 Feb 2012
  9. 20%

    Microsoft Visio Viewer 2010 Gold and SP1 does not properly handle memory during the parsing of files, which allows remote attackers to execute arbitrary code via crafted attributes in a Visio file, aka "VSD File...

    CVSS9.3Published14 Feb 2012
Precursor Intelligence

Running Visio Viewer? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 9 published vulnerabilities listed under the name Visio Viewer, across 4 versions. The most recent Visio Viewer flaw added to the known-exploited list is CVE-2016-3235, on 3 November 2021.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2016-3235.

Each flaw names its own versions, usually as ranges. The newest, CVE-2016-3235, affects 2007-sp3, 2010. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Visio Viewer. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.