CVE-2019-5786

CRITICALNVD 6.59.0▲
EchelonGraph scoreHIGH confidence

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. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 61%CVSS: 6.5Exploit: cisa kev · ssvc active · Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed 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
81
EG Risk 81/100CISA SSVC

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 computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 27, 2019

Last Modified

October 24, 2025

Advisory Details (3)

Auto-updated Jun 12, 2026
⚠️ Active exploitation confirmed. 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
generic
https://crbug.com/936448
generic🔴 Active Exploitation

Chrome Releases: Stable Channel Update for Desktop

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatchromium-browser-0:72.0.3626.121-1.el6_102019-03-11redhat

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 49× in last 7d / 237× 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,015 total refreshes for this CVE.

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

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-46812✓ verified
    First seen May 8, 2019

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

    Open source ↗
  • Metasploitexploit/windows/browser/chrome_filereader_uaf✓ verified
    First seen Mar 21, 2019

    Chrome 72.0.3626.119 FileReader UaF exploit for Windows 7 x86

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

    FileReader Exploit

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(6)

What is CVE-2019-5786?
CVE-2019-5786 is a critical vulnerability 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 CVE-2019-5786 disclosed?
CVE-2019-5786 was first published on June 27, 2019, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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.

Book a Demo →Browse All CVEs