A remote code execution vulnerability exists in Microsoft Word software when it fails to properly handle objects in memory. An attacker who successfully exploited the vulnerability could use a specially crafted file to perform actions in the security context of the current user. The file could then take actions on behalf of the logged-on user with the same permissions as the current user. To exploit the vulnerability, a user must open a specially crafted file with an affected version of Microsoft Word software. Two possible email attack scenarios exist for this vulnerability: • With the first email attack scenario, an attacker could send a specially crafted email message to the user and wait for the user to click on the message. When the message renders via Microsoft Word in the Outlook Preview Pane, an attack could be triggered. • With the second scenario, an attacker could attach a specially crafted file to an email, send it to a user, and convince them to open it. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file that is designed to exploit the vulnerability. However, an attacker would have no way to force the user to visit the website. Instead, an attacker would have to convince the user to click a link, typically by way of an enticement in an email or other message, and then convince the user to open the specially crafted file. The security update addresses the vulnerability by correcting how Microsoft Word handles files in memory. For users who view their emails in Outlook, the Preview Pane attack vector can be mitigated by disabling this feature. The following registry keys can be set to disable the Preview Pane in Outlook on Windows, either via manual editing of the registry or by modifying Group Policy. Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Outlook 2010: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Options DWORD: DisableReadingPane Value: 1 Outlook 2013: HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Options DWORD: DisableReadingPane Value: 1 Outlook 2016, Outlook 2019, and Office 365 ProPlus: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options DWORD: DisableReadingPane Value: 1
CVE-2019-1201
“—” beside the score: it is equal to NVD's CVSS score.
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHmedium confidence
- EG Risk
- 37EG Risk 37/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation4.9% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 4.9%
- EPSS %ILE
- 92nd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 4.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-21). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
August 14, 2019
Last Modified
February 20, 2026
Advisory Details (1)
Auto-updated Oct 21, 2026Security Update Guide - Microsoft Security Response Center
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1201Vendor Advisories for CVE-2019-1201(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Data Freshness Timeline
(refreshed 11× in last 7d / 34× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 92 of 166 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 74 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-22 16:28 UTCEPSS rescoreEPSS 4.9% · 92nd percentile
- 2026-10-21 18:36 UTCEG score recompute
- 2026-10-21 18:36 UTCVendor advisory
- 2026-10-21 18:36 UTCGHSA enrichmentGHSA-mhjc-pqhq-cf8c · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-21 16:27 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-20 16:27 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-19 16:27 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-18 16:27 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-18 09:56 UTCEG score recompute
- 2026-10-17 16:28 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-16 16:31 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-15 16:27 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-14 16:28 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-13 16:27 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-12 20:03 UTCEG score recompute
- 2026-10-12 16:28 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-12 00:27 UTCEG score recompute
- 2026-10-11 13:42 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-10 19:55 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-09 20:03 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-08 16:37 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-07 23:43 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-06 15:12 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-05 17:39 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-04 23:18 UTCEPSS rescoreEPSS 4.9% · 91st percentile
Show 67 moreShow fewer
- 2026-10-03 14:22 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-30 14:59 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-30 10:09 UTCEG score recompute
- 2026-09-28 13:46 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-27 13:40 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-26 15:54 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-26 00:20 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-24 13:59 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-23 13:43 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-22 14:43 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-21 20:28 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-20 20:10 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-18 19:22 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-17 19:22 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-16 14:04 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-15 03:05 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-13 16:42 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-12 14:56 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-11 14:48 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-11 09:32 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-07 15:57 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-06 13:44 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-05 15:24 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-04 13:56 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-02 14:07 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-09-01 03:32 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-30 19:13 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-30 01:18 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-28 21:36 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-27 14:21 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-26 14:42 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-25 13:45 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-24 14:11 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-21 23:45 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-20 22:51 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-19 17:00 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-18 13:44 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-17 13:43 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-16 14:52 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-16 02:10 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-15 01:26 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-12 13:47 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-09 13:43 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-08 16:33 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-07 16:23 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-06 13:43 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-05 19:13 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-04 15:05 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-02 02:23 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-08-01 04:12 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-30 16:24 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-30 01:27 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-28 15:32 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-26 14:51 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-25 14:14 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-24 14:14 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-23 14:15 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-23 01:39 UTCEG score recompute
- 2026-07-22 22:19 UTCEG score recompute
- 2026-07-22 14:05 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-21 15:22 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-20 17:04 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-19 14:28 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-19 02:26 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-18 10:01 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-16 16:59 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-07-15 16:55 UTCEPSS rescoreEPSS 4.9% · 91st percentile
Frequently asked(5)
What is CVE-2019-1201?
When was CVE-2019-1201 made public?
Is CVE-2019-1201 actively exploited?
What is the CVSS score of CVE-2019-1201?
How do I remediate CVE-2019-1201?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2019-1201
Is Your Infrastructure Affected by CVE-2019-1201?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.