Threats / Google / CVE-2024-5274
CVE-2024-5274
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Google Chromium V8 contains a type confusion vulnerability allowing remote code execution through crafted HTML pages, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
A type confusion flaw in V8 enables unauthenticated remote attackers to achieve arbitrary code execution by delivering malicious HTML. Active exploitation in the wild increases risk despite low EPSS score.
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
15 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-28).
Probability (EPSS)
EPSS 0.1002 — 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-843 Type Confusion — 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 exploits type confusion in V8's object handling to corrupt memory state.
Business
Users visiting attacker-controlled or compromised websites face immediate code execution risk without user interaction beyond normal browsing.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the corrupted memory to break out of the V8 sandbox and gain renderer process privileges.
Business
Renderer compromise exposes user data, credentials, and session tokens accessible to the browser process.
3
Lateral reach — past segmentation narrative 3
Attacker
I escalate from renderer to system level through additional OS-level exploits or browser sandbox bypasses.
Business
Full system compromise becomes possible, enabling malware installation, data theft, or lateral movement within enterprise networks.
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