Skip to main content
Mallory
MediumVulnerability

CVE-2016-3366: Microsoft Office Spoofing Vulnerability (CVE-2016-3366)

Published Sep 14, 2016 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3
EPSS16.2%97th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2016-3366CWE-20

CVE-2016-3366 is a vulnerability in Microsoft Outlook (versions 2007 SP3, 2010 SP2, 2013 SP1, 2013 RT SP1, 2016, and 2016 for Mac) where improper implementation of RFC 2046 allows remote attackers to craft MIME data in email attachments that can bypass virus or spam detection mechanisms. The vulnerability arises from Outlook's failure to correctly parse or validate MIME types, enabling attackers to disguise malicious content.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows attackers to bypass security controls such as antivirus or antispam filters, potentially leading to the delivery and execution of malicious payloads on the target system. This can result in malware infection, data exfiltration, or further compromise of the affected system.

Mitigation

If you can’t patch tonight, do this now.

As a temporary measure, organizations can implement additional email gateway filtering and content inspection to detect suspicious or malformed MIME attachments. User awareness training to avoid opening unexpected attachments can also reduce risk until patches are applied.

Remediation

Patch, then assume compromise.

Apply the security updates provided by Microsoft for the affected Outlook versions. These updates address the improper MIME parsing and ensure compliance with RFC 2046, closing the bypass vector.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationOutlookapplication
FAQ

Frequently asked questions

Is CVE-2016-3366 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2016-3366?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2016-3366.
Is there a patch for CVE-2016-3366?
Apply the security updates provided by Microsoft for the affected Outlook versions. These updates address the improper MIME parsing and ensure compliance with RFC 2046, closing the bypass vector.
What products are affected by CVE-2016-3366?
Microsoft Corporation Outlook.
How severe is CVE-2016-3366?
CVE-2016-3366 has a CVSS v3 score of 6.5 (Medium) and an EPSS score of 16.2% (97th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware3Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.