Skip to content
skopnix

CVE-2019-5825 · Published 25 Nov 2019

Google Chromium V8

On CISA's KEV list 926 days after disclosure; 3 public exploits.

Google Chromium V8 Engine contains an out-of-bounds write vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.

CISA required action (federal due date 22 Jun 2022): Apply updates per vendor instructions.

Signals

KEV, exploited in the wild
yes, added 8 Jun 2022, due 22 Jun 2022
EPSS, 30-day forecast
56%, 99th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.

Timeline 13 Nov 2019 to today

821 days from the first proof of concept to the KEV listing
20212023202420252026Metasploit 13 Nov 2019Disclosed 25 Nov 2019First PoC 9 Mar 2020KEV 8 Jun 2022today
  1. Metasploit
  2. Disclosed+12 d
  3. First PoC+105 d
  4. KEV+821 d

821 days from the first proof of concept to the KEV listing

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 0 dispatches

No dispatch on our wire has named this CVE yet.

Public exploit code 3 known · links only

GitHub PoCs 1Metasploit 1Exploit-DB 1

GitHub PoCs, by trust then stars1

  1. first seen by skopnix 18 Oct 2026

Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.

Metasploit1

  1. This module exploits an issue in Chrome 73.0.3683.86 (64 bit). The exploit corrupts the length of a float in order to modify the backing store of a typed array. The typed array can then be used to read and write arbitrary memory. The exploit then uses WebAssembly in order to allocate a region of RWX memory, which is then replaced with the payload. The payload is executed within the sandboxed renderer process, so the browser must be run

    ruby · first seen by skopnix 18 Oct 2026

Exploit-DB1

  1. created 9 Mar 2020

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check