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 release is recorded for CVE-2016-3351 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2016-3351 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2016-3351 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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 26.5%, 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.

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 August 14, 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 · ACTIVELY EXPLOITED

MEDIUM severity

CVE-2016-3351 — Microsoft

MEDIUM

CVE-2016-3351 is a medium-severity (CVSS 6.5) vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-05-24) and has been used in ransomware campaigns — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

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

Aug 14, 2026

Affected

2 products

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-05-24 — including use in ransomware campaigns. Federal agencies were required to remediate by 2022-06-14.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2016-3351.

EPSS Exploitation Probability

via FIRST.org ↗

26.5%probability of exploitation in next 30 days

Moderate Risk+0.20%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2016-3351 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

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

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2016-3351 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-3351 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2016-3351 — Microsoft

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2016-3351 in your dependencies?