CVE-2016-7267

What it is

Microsoft Excel 2010 SP2, 2013 SP1, 2013 RT SP1, and 2016 misparses file formats, which makes it easier for remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office Security Feature Bypass Vulnerability."

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data tampering.

Exploit odds

20.0% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2016-12-20 06:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:52 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 20.0% in the next 30 days (EPSS).
• Severity: 5.5 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2016-12-20 06:59 UTC

Last modified

2026-06-17 00:52 UTC

Exploit probability

20.0% · EPSS, next 30 days

Weakness

CWE-20 · Improper input validation

Record status

Modified

Affected

• Microsoft Excel 2010
• Microsoft Excel 2013
• Microsoft Excel 2016

Attack profile CVSS 3.0 · 5.5

Attack vector

Local

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-7267.md and follow it. Check whether this project is affected by CVE-2016-7267. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge