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."
CVE-2017-11774
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 60%
- EPSS %ILE
- 99%
- KEV
- ⚠ Exploited
Published
October 13, 2017
Last Modified
June 17, 2026
Advisory Details (5)
Auto-updated May 19, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-11774SensePost | Outlook Home Page – Another Ruler Vector
https://sensepost.com/blog/2017/outlook-home-page-another-ruler-vector/Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-11774Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 90× in last 7d / 385× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 1,278 total refreshes for this CVE.
- 2026-09-08 11:27 UTCVendor advisory
- 2026-09-08 11:27 UTCGHSA enrichment
- 2026-09-08 07:20 UTCVendor advisory
- 2026-09-08 07:20 UTCGHSA enrichment
- 2026-09-08 03:13 UTCVendor advisory
- 2026-09-08 03:13 UTCGHSA enrichment
- 2026-09-07 23:05 UTCVendor advisory
- 2026-09-07 23:05 UTCGHSA enrichment
- 2026-09-07 18:58 UTCVendor advisory
- 2026-09-07 18:58 UTCGHSA enrichment
- 2026-09-07 14:51 UTCGHSA enrichment
- 2026-09-07 10:43 UTCVendor advisory
- 2026-09-07 10:43 UTCGHSA enrichment
- 2026-09-07 06:34 UTCVendor advisory
- 2026-09-07 06:34 UTCGHSA enrichment
- 2026-09-07 02:23 UTCVendor advisory
- 2026-09-07 02:23 UTCGHSA enrichment
- 2026-09-06 22:15 UTCVendor advisory
- 2026-09-06 22:15 UTCGHSA enrichment
- 2026-09-06 18:08 UTCVendor advisory
- 2026-09-06 18:08 UTCGHSA enrichment
- 2026-09-06 14:00 UTCEG score recompute
- 2026-09-06 14:00 UTCVendor advisory
- 2026-09-06 14:00 UTCGHSA enrichment
- 2026-09-06 09:53 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-06 09:53 UTCGHSA enrichment
- 2026-09-06 05:46 UTCVendor advisory
- 2026-09-06 05:46 UTCGHSA enrichment
- 2026-09-06 01:39 UTCVendor advisory
- 2026-09-06 01:39 UTCGHSA enrichment
- 2026-09-05 21:32 UTCVendor advisory
- 2026-09-05 21:32 UTCGHSA enrichment
- 2026-09-05 17:25 UTCEG score recompute
- 2026-09-05 17:25 UTCVendor advisory
- 2026-09-05 17:25 UTCGHSA enrichment
- 2026-09-05 13:17 UTCVendor advisory
- 2026-09-05 13:17 UTCGHSA enrichment
- 2026-09-05 09:10 UTCVendor advisory
- 2026-09-05 09:10 UTCGHSA enrichment
- 2026-09-05 05:03 UTCVendor advisory
- 2026-09-05 05:03 UTCGHSA enrichment
- 2026-09-05 00:55 UTCVendor advisory
- 2026-09-05 00:55 UTCGHSA enrichment
- 2026-09-04 20:47 UTCVendor advisory
- 2026-09-04 20:47 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 16:39 UTCEG score recompute
- 2026-09-04 16:39 UTCVendor advisory
- 2026-09-04 16:39 UTCGHSA enrichment
- 2026-09-04 13:56 UTCEPSS rescore
- 2026-09-04 12:32 UTCVendor advisory
- 2026-09-04 12:32 UTCGHSA enrichment
- 2026-09-04 08:25 UTCEG score recompute
- 2026-09-04 08:25 UTCVendor advisory
- 2026-09-04 08:25 UTCGHSA enrichment
- 2026-09-04 05:01 UTCEPSS rescore
- 2026-09-04 04:16 UTCVendor advisory
- 2026-09-04 04:16 UTCGHSA enrichment
- 2026-09-04 00:08 UTCVendor advisory
- 2026-09-04 00:08 UTCGHSA enrichment
- 2026-09-03 20:01 UTCVendor advisory
- 2026-09-03 20:01 UTCGHSA enrichment
- 2026-09-03 15:54 UTCVendor advisory
- 2026-09-03 15:54 UTCGHSA enrichment
- 2026-09-03 11:47 UTCVendor advisory
- 2026-09-03 11:46 UTCGHSA enrichment
- 2026-09-03 07:36 UTCVendor advisory
- 2026-09-03 07:36 UTCGHSA enrichment
- 2026-09-03 03:27 UTCVendor advisory
- 2026-09-03 03:27 UTCGHSA enrichment
- 2026-09-02 23:17 UTCVendor advisory
- 2026-09-02 23:16 UTCGHSA enrichment
- 2026-09-02 19:09 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 14:58 UTCEG score recompute
- 2026-09-02 14:58 UTCVendor advisory
- 2026-09-02 14:58 UTCGHSA enrichment
- 2026-09-02 14:07 UTCEPSS rescore
- 2026-09-02 10:44 UTCVendor advisory
- 2026-09-02 10:44 UTCGHSA enrichment
- 2026-09-02 06:33 UTCVendor advisory
- 2026-09-02 06:33 UTCGHSA enrichment
- 2026-09-02 02:24 UTCVendor advisory
- 2026-09-02 02:24 UTCGHSA enrichment
- 2026-09-01 22:16 UTCVendor advisory
- 2026-09-01 22:16 UTCGHSA enrichment
- 2026-09-01 18:09 UTCVendor advisory
- 2026-09-01 18:09 UTCGHSA enrichment
- 2026-09-01 14:02 UTCVendor advisory
- 2026-09-01 14:02 UTCGHSA enrichment
- 2026-09-01 09:53 UTCVendor advisory
- 2026-09-01 09:52 UTCGHSA enrichment
- 2026-09-01 05:43 UTCVendor advisory
- 2026-09-01 05:43 UTCGHSA enrichment
- 2026-09-01 01:33 UTCVendor advisory
- 2026-09-01 01:33 UTCGHSA enrichment
- 2026-08-31 21:21 UTCVendor advisory
- 2026-08-31 21:21 UTCGHSA enrichment
- 2026-08-31 17:14 UTCVendor advisory
- 2026-08-31 17:14 UTCGHSA enrichment
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-119
- CVE-2003-0819EG 10.0EPSS p99HIGH
- CVE-2003-0903EG 10.0EPSS p98HIGH
- CVE-2003-1339EG 10.0EPSS p99HIGH
- CVE-2003-0095EG 10.0EPSS p96HIGH
- CVE-2002-2227EG 10.0HIGH
- CVE-2002-2248EG 10.0EPSS p93HIGH
- CVE-2002-2250EG 10.0EPSS p94HIGH
- CVE-2002-2251EG 10.0EPSS p93HIGH
- CVE-2002-2253EG 10.0EPSS p93HIGH
- CVE-2002-2257EG 10.0EPSS p92HIGH
Frequently asked(6)
What is CVE-2017-11774?
When was CVE-2017-11774 disclosed?
Is CVE-2017-11774 actively exploited?
What is the CVSS score of CVE-2017-11774?
Which products are affected by CVE-2017-11774?
How do I remediate CVE-2017-11774?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-11774
Is Your Infrastructure Affected by CVE-2017-11774?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.