Threats / Google / CVE-2024-7965
CVE-2024-7965
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Google Chromium V8 contains an inappropriate implementation vulnerability allowing remote attackers to exploit heap corruption through crafted HTML pages, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
A remote attacker can trigger heap corruption in V8 by delivering a malicious HTML page to a victim's browser. Exploitation requires user interaction (visiting a webpage) but no authentication. The vulnerability is actively exploited in the wild.
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
6 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-08-28).
Probability (EPSS)
EPSS 0.17227 — 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-358 CWE-358.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
WeaknessCWE-358 · CWE-358
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
I craft a malicious HTML page and host it on a website or distribute it via email/messaging.
Business
Users visiting the attacker's page without additional security controls face browser compromise and potential data theft or system access.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger heap corruption in the V8 JavaScript engine when the victim's browser parses my HTML.
Business
Heap corruption can lead to memory disclosure, arbitrary code execution, or denial of service affecting browser stability and user trust.
3
Lateral reach — past segmentation narrative 3
Attacker
I achieve code execution within the browser process sandbox to escalate privileges or pivot to the host system.
Business
Successful exploitation enables data exfiltration, malware installation, or lateral movement within corporate networks using compromised endpoints.
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