CVE-2019-5825

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-06-08), 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, ghsa, nvd
Trending — 5 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: 56%CVSS: 6.5Exploit: cisa kev · ssvc active · Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

Out of bounds write in JavaScript in Google Chrome prior to 73.0.3683.86 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

CVSS v3
6.5
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 computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
56%
EPSS %ILE
99%
KEV
⚠ Exploited

Published

November 25, 2019

Last Modified

October 24, 2025

Advisory Details (3)

Auto-updated Jun 12, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 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-5825

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatchromium-browser-0:74.0.3729.108-1.el6_102019-05-07redhat

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.

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 62× in last 7d / 380× 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 761 total refreshes for this CVE.

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

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-48183✓ verified
    First seen Mar 9, 2020

    Google Chrome 72 and 73 - Array.map Out-of-Bounds Write (Metasploit)

    Open source ↗
  • GitHub PoCtimwr/CVE-2019-5825
    First seen Nov 23, 2019
    Open source ↗
  • Metasploitexploit/multi/browser/chrome_array_map✓ verified
    First seen Mar 7, 2019

    Google Chrome 72 and 73 Array.map exploit

    Open source ↗

Frequently asked(6)

What is CVE-2019-5825?
CVE-2019-5825 is a critical vulnerability published on November 25, 2019. Out of bounds write in JavaScript in Google Chrome prior to 73.0.3683.86 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
When was CVE-2019-5825 disclosed?
CVE-2019-5825 was first published in the National Vulnerability Database on November 25, 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-5825 actively exploited?
Yes. CISA added CVE-2019-5825 to the Known Exploited Vulnerabilities catalog on June 8, 2022, affecting Google Chromium V8. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2019-5825?
CVE-2019-5825 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.
Which products are affected by CVE-2019-5825?
CVE-2019-5825 affects Google Chromium V8. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2019-5825?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-5825, 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-5825

Explore →

Is Your Infrastructure Affected by CVE-2019-5825?

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