CVE-2019-5786

CRITICALNVD 6.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-05-23), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 6.5 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 6.5 MEDIUM under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild

Also known asEUVD-2020-0957 (ENISA EUVD) · GHSA-c2gp-86p4-5935 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at every mission impact level
CISA-KEV: ExploitedEPSS PROB: 61%CVSS: 6.5Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

Object lifetime issue in Blink in Google Chrome prior to 72.0.3626.121 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.

CVSS v3
6.5
EG Score
9.0CRITICALhigh confidence
EG Risk
69
EG Risk 69/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
61%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 6.5 MEDIUM.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
61% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2019-5786

Published

June 27, 2019

Last Modified

October 24, 2025

Advisory Details (3)

Auto-updated Oct 27, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa.
CISA🔴 Active Exploitation

Known 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-2019-5786
Web page

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2019/03/stable-channel-update-for-desktop.html

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatchromium-browser-0:72.0.3626.121-1.el6_102019-03-11redhat
npmpuppeteer @ 1.13.0 (fixes < 1.13.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 72.0.3626.121-1: fixed in 72.0.3626.121-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 72.0.3626.121-1: fixed in 72.0.3626.121-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 72.0.3626.121-1: fixed in 72.0.3626.121-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 72.0.3626.121-1: fixed in 72.0.3626.121-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
chromium0.9-8 ... 72.0.3626.96-1~deb9u2 (30 versions)
  • every version up to 72.0.3626.122-1~deb9u1: fixed in 72.0.3626.122-1~deb9u1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
puppeteer—
  • every version up to 1.13.0: fixed in 1.13.0
—

Weakness 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 24× in last 7d / 137× 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 100 of 1,135 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. None are among the latest 100 rows. The 1,035 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 09:55 UTCEG score recompute
  2. 2026-11-02 09:55 UTCVendor advisory
  3. 2026-11-02 09:55 UTCGHSA enrichmentGHSA-c2gp-86p4-5935 · GitHub severity MODERATE · GitHub CVSS 6.5
  4. 2026-11-01 16:28 UTCEPSS rescoreEPSS 61% · 99th percentile
  5. 2026-11-01 10:55 UTCVendor advisory
  6. 2026-11-01 10:55 UTCGHSA enrichmentGHSA-c2gp-86p4-5935 · GitHub severity MODERATE · GitHub CVSS 6.5
  7. 2026-11-01 08:39 UTCGHSA enrichmentGHSA-c2gp-86p4-5935 · GitHub severity MODERATE · GitHub CVSS 6.5
  8. 2026-11-01 08:39 UTCEG score recompute
  9. 2026-10-31 16:28 UTCEPSS rescoreEPSS 61% · 99th percentile
  10. 2026-10-31 11:54 UTCEG score recompute
  11. 2026-10-31 11:54 UTCVendor advisory
  12. 2026-10-30 16:29 UTCEPSS rescoreEPSS 61% · 99th percentile
  13. 2026-10-30 12:52 UTCEG score recompute
  14. 2026-10-30 12:52 UTCVendor advisory
  15. 2026-10-29 16:28 UTCEPSS rescoreEPSS 61% · 99th percentile
  16. 2026-10-29 13:52 UTCEG score recompute
  17. 2026-10-29 13:52 UTCVendor advisory
  18. 2026-10-28 16:27 UTCEPSS rescoreEPSS 61% · 99th percentile
  19. 2026-10-28 14:51 UTCEG score recompute
  20. 2026-10-28 14:51 UTCVendor advisory
  21. 2026-10-27 16:27 UTCEPSS rescoreEPSS 61% · 99th percentile
  22. 2026-10-27 15:47 UTCVendor advisory
  23. 2026-10-26 16:45 UTCEG score recompute
  24. 2026-10-26 16:45 UTCVendor advisory
  25. 2026-10-25 17:45 UTCEG score recompute
Show 75 more
  1. 2026-10-25 17:45 UTCVendor advisory
  2. 2026-10-25 16:27 UTCEPSS rescoreEPSS 61% · 99th percentile
  3. 2026-10-24 18:44 UTCEG score recompute
  4. 2026-10-24 18:44 UTCVendor advisory
  5. 2026-10-24 16:28 UTCEPSS rescoreEPSS 61% · 99th percentile
  6. 2026-10-23 19:43 UTCEG score recompute
  7. 2026-10-23 19:43 UTCVendor advisory
  8. 2026-10-23 16:27 UTCEPSS rescoreEPSS 61% · 99th percentile
  9. 2026-10-22 20:39 UTCEG score recompute
  10. 2026-10-22 20:39 UTCVendor advisory
  11. 2026-10-22 16:28 UTCEPSS rescoreEPSS 61% · 99th percentile
  12. 2026-10-21 21:36 UTCEG score recompute
  13. 2026-10-21 21:36 UTCVendor advisory
  14. 2026-10-21 16:27 UTCEPSS rescoreEPSS 61% · 99th percentile
  15. 2026-10-20 22:34 UTCEG score recompute
  16. 2026-10-20 22:34 UTCVendor advisory
  17. 2026-10-20 16:28 UTCEPSS rescoreEPSS 61% · 99th percentile
  18. 2026-10-19 23:34 UTCEG score recompute
  19. 2026-10-19 23:34 UTCVendor advisory
  20. 2026-10-19 16:27 UTCEPSS rescoreEPSS 61% · 99th percentile
  21. 2026-10-19 00:32 UTCEG score recompute
  22. 2026-10-19 00:32 UTCVendor advisory
  23. 2026-10-18 16:27 UTCEPSS rescoreEPSS 61% · 99th percentile
  24. 2026-10-18 09:43 UTCEG score recompute
  25. 2026-10-18 01:30 UTCEG score recompute
  26. 2026-10-18 01:30 UTCVendor advisory
  27. 2026-10-17 02:26 UTCEG score recompute
  28. 2026-10-17 02:26 UTCVendor advisory
  29. 2026-10-16 16:32 UTCEPSS rescoreEPSS 61% · 99th percentile
  30. 2026-10-16 03:25 UTCEG score recompute
  31. 2026-10-16 03:25 UTCVendor advisory
  32. 2026-10-15 16:27 UTCEPSS rescoreEPSS 61% · 99th percentile
  33. 2026-10-15 04:23 UTCEG score recompute
  34. 2026-10-15 04:23 UTCVendor advisory
  35. 2026-10-14 16:28 UTCEPSS rescoreEPSS 61% · 99th percentile
  36. 2026-10-14 05:21 UTCEG score recompute
  37. 2026-10-14 05:21 UTCVendor advisory
  38. 2026-10-13 16:28 UTCEPSS rescoreEPSS 61% · 99th percentile
  39. 2026-10-13 06:19 UTCVendor advisory
  40. 2026-10-12 19:53 UTCEG score recompute
  41. 2026-10-12 16:28 UTCEPSS rescoreEPSS 61% · 99th percentile
  42. 2026-10-12 07:18 UTCVendor advisory
  43. 2026-10-12 03:29 UTCVendor advisory
  44. 2026-10-11 23:44 UTCVendor advisory
  45. 2026-10-11 19:56 UTCEG score recompute
  46. 2026-10-11 19:56 UTCVendor advisory
  47. 2026-10-11 16:10 UTCEG score recompute
  48. 2026-10-11 16:10 UTCVendor advisory
  49. 2026-10-11 13:42 UTCEPSS rescoreEPSS 61% · 99th percentile
  50. 2026-10-11 12:25 UTCEG score recompute
  51. 2026-10-11 12:25 UTCVendor advisory
  52. 2026-10-11 08:37 UTCVendor advisory
  53. 2026-10-11 04:51 UTCVendor advisory
  54. 2026-10-11 01:06 UTCVendor advisory
  55. 2026-10-10 21:18 UTCEG score recompute
  56. 2026-10-10 21:18 UTCVendor advisory
  57. 2026-10-10 19:56 UTCEPSS rescoreEPSS 61% · 99th percentile
  58. 2026-10-10 17:30 UTCVendor advisory
  59. 2026-10-10 13:44 UTCVendor advisory
  60. 2026-10-10 09:58 UTCVendor advisory
  61. 2026-10-10 06:13 UTCVendor advisory
  62. 2026-10-10 02:27 UTCVendor advisory
  63. 2026-10-09 22:42 UTCEG score recompute
  64. 2026-10-09 22:42 UTCVendor advisory
  65. 2026-10-09 20:03 UTCEPSS rescoreEPSS 61% · 99th percentile
  66. 2026-10-09 18:56 UTCVendor advisory
  67. 2026-10-09 15:12 UTCVendor advisory
  68. 2026-10-09 11:26 UTCVendor advisory
  69. 2026-10-09 07:41 UTCVendor advisory
  70. 2026-10-09 03:56 UTCVendor advisory
  71. 2026-10-09 00:10 UTCVendor advisory
  72. 2026-10-08 20:25 UTCVendor advisory
  73. 2026-10-08 16:40 UTCEG score recompute
  74. 2026-10-08 16:40 UTCVendor advisory
  75. 2026-10-08 16:37 UTCEPSS rescoreEPSS 61% · 99th percentile

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-46812✓ verified
    Published May 8, 2019

    Google Chrome 72.0.3626.119 - 'FileReader' Use-After-Free (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/browser/chrome_filereader_uaf✓ verified
    Published May 8, 2019

    Chrome 72.0.3626.119 FileReader UaF exploit for Windows 7 x86

    Open source ↗
  • GitHub PoCexodusintel/CVE-2019-5786
    Published Mar 20, 2019

    FileReader Exploit

    Open source ↗

Frequently asked(6)

What is CVE-2019-5786?
CVE-2019-5786 is a critical-severity vulnerability; its CVE record was published on June 27, 2019. Object lifetime issue in Blink in Google Chrome prior to 72.0.3626.121 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
When was the CVE record for CVE-2019-5786 published?
The CVE record for CVE-2019-5786 was published on June 27, 2019. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2025; the record at its source may have been updated since.
Is CVE-2019-5786 actively exploited?
Yes. CISA added CVE-2019-5786 to the Known Exploited Vulnerabilities catalog on May 23, 2022, affecting Google Chrome Blink. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2019-5786?
CVE-2019-5786 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2019-5786?
CVE-2019-5786 affects Google Chrome Blink. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2019-5786?
A fix for CVE-2019-5786 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-5786

Explore →

Is Your Infrastructure Affected by CVE-2019-5786?

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