How severe is CVE-2016-3351?

CVE-2016-3351 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2016-3351?

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

How do I fix CVE-2016-3351?

No fixed version has been published for CVE-2016-3351 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-3351 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2016-3351, including 4 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-3351?

CVE-2016-3351 has an EPSS (Exploit Prediction Scoring System) score of 45.4%, placing it in the 98th 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. This score warrants monitoring and prompt remediation.

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

Yes. CVE-2016-3351 (Microsoft Internet Explorer and Edge Information Disclosure Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-05-24. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-06-14. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. 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-3351?

CVE-2016-3351 affects microsoft edge; microsoft internet explorer (3 versions, e.g. 9, 10, 11). Check the affected-products list on this page against your deployed version to confirm exposure.

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

CVE-2016-3351 was published on September 14, 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 2022-05-24 — agencies required to remediate by 2022-06-14 · Ransomware

CVE-2016-3351

MEDIUM

Microsoft Internet Explorer 9 through 11 and Microsoft Edge allow remote attackers to obtain sensitive information via a crafted web site, aka "Microsoft Browser Information Disclosure Vulnerability."

Published

Sep 14, 2016

Updated

Apr 22, 2026

Affected

0 pkgs

Patched

None yet

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

45.4%probability of exploitation in next 30 days

High Risk98th 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

Affected Products

2 products · 4 configurations

Application

edgemicrosoft

all

Application

internet explorermicrosoft

3 versions

91011

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.

Microsoft Internet Explorer 9 through 11 and Microsoft Edge allow remote…

portal.msrc.microsoft.comMSSep 2016

Microsoft Internet Explorer 9 through 11 and Microsoft Edge allow remote…

docs.microsoft.comGoogle-sheetSep 2016

Microsoft Internet Explorer 9 through 11 and Microsoft Edge allow remote…

cisa.govCISAMay 2022

Microsoft Internet Explorer 9 through 11 and Microsoft Edge allow remote…

brokenbrowser.comNVDJul 2024

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-3351 in your stack?

O3 detects CVE-2016-3351 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

6.5/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction

Required

S:Scope

Unchanged

C:Confidentiality

High

I:Integrity

None

A:Availability

None

Raw vector

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

Weaponization

No known public exploit tooling found.

Timeline

First exploit

Sep 13, 2016

Disclosed

Sep 14, 2016

KEV added

May 24, 2022

Last updated

Apr 22, 2026

Identifiers

CVE-2016-3351

References

Advisorysecurityfocus.com Advisorysecuritytracker.com Advisorysecuritytracker.com Advisorysecurityfocus.com Advisorysecuritytracker.com Advisorysecuritytracker.com Fixdocs.microsoft.com Fixdocs.microsoft.com Fixdocs.microsoft.com Fixdocs.microsoft.com Exploit / PoCbrokenbrowser.com Exploit / PoCbrokenbrowser.com Webcisa.gov

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