CVE-2017-11774

Microsoft Outlook 2010 SP2, Outlook 2013 SP1 and RT SP1, and Outlook 2016 allow an attacker to execute arbitrary commands, due to how Microsoft Office handles objects in memory, aka "Microsoft Outlook Security Feature Bypass Vulnerability."

Exploited in the wild: Yesadded 2021-11-03 · due 2022-05-03. An observation, not a forecast.
EPSS · 30-day forecast: 60%Chance of exploitation in the next 30 days, 99th percentile of all CVEs. A forecast; KEV outranks it.
CVSS · NVD · HIGH: 7.8CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Internet exposure: not stated by sourcesNo exposure census on this CVE's dispatches.

Exploits

not checked

Not checked yet. Our exploit watch has not looked at this CVE, so this says nothing either way.

On the wire

0 dispatches

No dispatch on our wire has named this CVE yet.

Cited as exploited by

APT33
1. “APT33 has attempted to exploit a known vulnerability in WinRAR (CVE-2018-20250), and attempted to gain remote code execution via a security bypass vulnerability (CVE-2017-11774).”
  cited as exploiting · source: attack.mitre.org ↗ · 2026-10-17
2. “The group used Ruler to configure a specially crafted Outlook Home Page URL to exploit the security bypass vulnerability CVE-2017-11774 , which was fixed shortly after it was discovered.”
  cited as exploiting · named nearby · source: microsoft.com ↗ · 2026-10-17
OilRig
1. “OilRig has also used CVE-2017-11774 to roll back the initial patch designed to protect against Home Page abuse.”
  cited as exploiting · source: attack.mitre.org ↗ · 2026-10-17

Each actor is cited by the quoted source, linked under the quote. A citation is that source's claim, not our confirmation.

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Follow on Telegram KEV RSS API

Check your stack

Paste what you run: the CVEs exploited in the wild against it, and who is cited as exploiting them, with the report.

Stack checkNo key. No signup.

Signals

Exploits

On the wire

Watch this one?