Threats / Google / CVE-2024-0519
CVE-2024-0519
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Out-of-bounds memory access in Chromium V8 engine allows remote attackers to trigger heap corruption through crafted HTML, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
Remote attacker exploits heap corruption via malicious webpage to potentially achieve code execution or denial of service in V8 JavaScript engine. Active exploitation observed in wild.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
8 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-01-17).
Probability (EPSS)
EPSS 0.03769 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chromium V8. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
Craft HTML page with malicious JavaScript to trigger out-of-bounds memory write in V8 engine
Business
User browsing compromised or attacker-controlled website experiences browser crash or code execution
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Achieve arbitrary code execution within browser process sandbox via heap corruption
Business
Attacker gains ability to steal user data, install malware, or pivot to system compromise
3
Lateral reach — past segmentation narrative 3
Attacker
Distribute exploit through ad networks, watering hole attacks, or social engineering
Business
Large-scale compromise of users across Chrome, Edge, Opera ecosystems without user interaction
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05