Threats / Google / CVE-2019-5825
CVE-2019-5825
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Out-of-bounds write in Chromium V8 engine allows remote code execution through crafted HTML, affecting Chrome, Edge, and Opera browsers.
Verdict
Today item — known-exploited.
Remote attacker can trigger heap corruption via malicious webpage to achieve code execution in the context of the browser process. High exploitability confirmed by active wild exploitation.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
2 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 2022-06-08).
Probability (EPSS)
EPSS 0.55925 — 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 V8 engine exploit payload to trigger out-of-bounds memory write
Business
User visits attacker-controlled or compromised website, browser process becomes compromised
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Achieve arbitrary code execution within browser sandbox through heap corruption
Business
Attacker gains ability to steal credentials, session tokens, and sensitive data from user's browsing context
3
Lateral reach — past segmentation narrative 3
Attacker
Escape browser sandbox or pivot to system-level compromise using secondary exploits
Business
Full system compromise possible, enabling malware installation, data exfiltration, or lateral movement
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