Threats / Google / CVE-2024-4761
CVE-2024-4761
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Google Chromium V8 contains an out-of-bounds memory write vulnerability exploitable via crafted HTML, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
An out-of-bounds write in V8 allows remote code execution through malicious web content. The vulnerability is actively exploited in the wild with low EPSS score but high impact potential across Chromium-based browsers.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
7 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-05-16).
Probability (EPSS)
EPSS 0.11007 — 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
I craft a malicious HTML page that triggers an out-of-bounds write in the V8 JavaScript engine.
Business
Users visiting attacker-controlled or compromised websites face arbitrary code execution within browser context.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the memory corruption to achieve code execution with browser process privileges.
Business
Attackers gain access to user credentials, browsing history, cached data, and can pivot to system compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I distribute the exploit through watering hole attacks or ad networks targeting Chromium browser users.
Business
Organizations face widespread endpoint compromise across their user base without requiring user interaction beyond normal browsing.
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