How severe is CVE-2016-7262?

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

Which packages are affected by CVE-2016-7262?

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

How do I fix CVE-2016-7262?

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

Yes. There are 1 known exploit references for CVE-2016-7262, including 1 in-the-wild exploitation 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-7262?

CVE-2016-7262 has an EPSS (Exploit Prediction Scoring System) score of 88.2%, placing it in the 100th 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-7262 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2016-7262 (Microsoft Office Security Feature Bypass Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-03-24. 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-7262?

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

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

CVE-2016-7262 was published on December 20, 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-03-03 — agencies required to remediate by 2022-03-24

CVE-2016-7262

HIGH

Microsoft Excel 2007 SP3, Excel 2010 SP2, Excel 2013 SP1, Excel 2013 RT SP1, Excel 2016, Office Compatibility Pack SP3, and Excel Viewer allow user-assisted remote attackers to execute…

Published

Dec 20, 2016

Updated

Apr 22, 2026

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

88.2%probability of exploitation in next 30 days

Very High Risk100th 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 Excel 2007 SP3, Excel 2010 SP2, Excel 2013 SP1, Excel 2013 RT SP1, Excel 2016, Office Compatibility Pack SP3, and Excel Viewer allow user-assisted remote attackers to execute arbitrary commands via a crafted cell that is mishandled upon a click, aka "Microsoft Office Security Feature Bypass Vulnerability."

Affected Products

3 products · 7 configurations

Application

excelmicrosoft

4 versions

2007201020132016

Application

excel viewermicrosoft

all

Application

office compatibility packmicrosoft

all

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 Excel 2007 SP3, Excel 2010 SP2, Excel 2013 SP1, Excel 2013 RT …

cisa.govCISAMar 2022

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-7262 in your stack?

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