CVE-2019-1054

MEDIUMNVD 5.05.0
EchelonGraph scoreMEDIUM confidence

Score 5.0 from GitHub Security Advisory published 2022-05-24. NVD baseline CVSS 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 2%CVSS: 5.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A security feature bypass vulnerability exists in Edge that allows for bypassing Mark of the Web Tagging (MOTW). Failing to set the MOTW means that a large number of Microsoft security technologies are bypassed. In a web-based attack scenario, an attacker could host a malicious website that is designed to exploit the security feature bypass. Alternatively, in an email or instant message attack scenario, the attacker could send the targeted user a specially crafted .url file that is designed to exploit the bypass. Additionally, compromised websites or websites that accept or host user-provided content could contain specially crafted content to exploit the security feature bypass. However, in all cases an attacker would have no way to force a user to view attacker-controlled content. Instead, an attacker would have to convince a user to take action. For example, an attacker could entice a user to either click a link that directs the user to the attacker's site or send a malicious attachment. The security update addresses the security feature bypass by correcting how Edge handles MOTW tagging.

CVSS v3
5.0
EG Score
5.0(medium)
EPSS
72.9%
KEV
Not listed

Published

June 12, 2019

Last Modified

May 20, 2025

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 9× in last 7d / 37× 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.

  1. 2026-07-07 13:43 UTCEPSS rescore
  2. 2026-07-06 16:25 UTCEPSS rescore
  3. 2026-07-06 16:25 UTCEPSS rescore
  4. 2026-07-06 02:20 UTCEPSS rescore
  5. 2026-07-05 02:27 UTCEPSS rescore
  6. 2026-07-04 06:28 UTCEPSS rescore
  7. 2026-07-01 15:03 UTCEPSS rescore
  8. 2026-07-01 15:03 UTCEPSS rescore
  9. 2026-06-30 23:20 UTCEPSS rescore
  10. 2026-06-28 14:04 UTCEPSS rescore
  11. 2026-06-28 04:54 UTCEPSS rescore
  12. 2026-06-28 04:54 UTCEPSS rescore
  13. 2026-06-27 03:06 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-24 14:03 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-23 21:31 UTCEPSS rescore
  19. 2026-06-23 21:30 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 14:54 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-19 19:23 UTCEPSS rescore
  25. 2026-06-19 19:23 UTCEPSS rescore
Show 41 more
  1. 2026-06-18 17:50 UTCEPSS rescore
  2. 2026-06-17 17:50 UTCEPSS rescore
  3. 2026-06-16 17:50 UTCEPSS rescore
  4. 2026-06-15 17:45 UTCEPSS rescore
  5. 2026-06-14 23:15 UTCEPSS rescore
  6. 2026-06-14 23:15 UTCEPSS rescore
  7. 2026-06-13 22:58 UTCEPSS rescore
  8. 2026-06-12 23:09 UTCEPSS rescore
  9. 2026-06-11 13:58 UTCEPSS rescore
  10. 2026-06-10 22:16 UTCEPSS rescore
  11. 2026-06-10 13:19 UTCEPSS rescore
  12. 2026-06-08 14:15 UTCEPSS rescore
  13. 2026-06-07 15:23 UTCEPSS rescore
  14. 2026-06-07 15:23 UTCEPSS rescore
  15. 2026-06-06 13:45 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-05 22:45 UTCEPSS rescore
  18. 2026-06-05 22:45 UTCEPSS rescore
  19. 2026-06-05 06:08 UTCEPSS rescore
  20. 2026-06-05 06:08 UTCEPSS rescore
  21. 2026-06-04 13:10 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-02 20:11 UTCEPSS rescore
  24. 2026-06-02 20:11 UTCEPSS rescore
  25. 2026-06-01 13:50 UTCEPSS rescore
  26. 2026-06-01 13:50 UTCEPSS rescore
  27. 2026-05-31 22:29 UTCEPSS rescore
  28. 2026-05-31 22:29 UTCEPSS rescore
  29. 2026-05-31 00:14 UTCEPSS rescore
  30. 2026-05-31 00:14 UTCEPSS rescore
  31. 2026-05-29 13:42 UTCEPSS rescore
  32. 2026-05-28 13:43 UTCEPSS rescore
  33. 2026-05-27 18:26 UTCEG score recompute
  34. 2026-05-27 18:26 UTCVendor advisory
  35. 2026-05-27 18:26 UTCGHSA enrichment
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-26 13:42 UTCEPSS rescore
  38. 2026-05-26 13:42 UTCEPSS rescore
  39. 2026-05-26 07:17 UTCEPSS rescore
  40. 2026-05-26 07:17 UTCEPSS rescore
  41. 2026-05-26 07:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-1054?
CVE-2019-1054 is a medium vulnerability published on June 12, 2019. A security feature bypass vulnerability exists in Edge that allows for bypassing Mark of the Web Tagging (MOTW). Failing to set the MOTW means that a large number of Microsoft security technologies are bypassed. In a web-based attack scenario, an attacker could host a malicious website that is…
When was CVE-2019-1054 disclosed?
CVE-2019-1054 was first published in the National Vulnerability Database on June 12, 2019, with the most recent update on May 20, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-1054 actively exploited?
CVE-2019-1054 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 72.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-1054?
CVE-2019-1054 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2019-1054?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-1054, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-1054

Explore →

Is Your Infrastructure Affected by CVE-2019-1054?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.