Skip to content
skopnix

CVE-2024-0519 · Published 16 Jan 2024

Google Chromium V8

On CISA's KEV list one day after disclosure; 3 public exploits.

Google Chromium V8 Engine contains an out-of-bounds memory access 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 7 Feb 2024): Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Signals

KEV, exploited in the wild
yes, added 17 Jan 2024, due 7 Feb 2024
EPSS, 30-day forecast
3.8%, 90th 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 16 Jan 2024 to today

850 days from the KEV listing to the first proof of concept
20252026Disclosed 16 Jan 2024KEV 17 Jan 2024First PoC 16 May 2026today
  1. Disclosed
  2. KEV+1 d
  3. First PoC+850 d

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

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 3Metasploit 0Exploit-DB 0

GitHub PoCs, by trust then stars3

  1. CVE-2024-0519 root cause analysis

    created 16 May 2026

  2. first seen by skopnix 18 Oct 2026

  3. 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.

References

Watch this one?

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

Telegram ↗KEV RSSAPIStack check