Threats / Google / CVE-2024-4947
CVE-2024-4947
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Google Chromium V8 vulnerability
Google Chromium V8 type confusion vulnerability allows remote code execution through crafted HTML pages. Actively exploited in the wild.
Verdict
Today item — known-exploited.
Type confusion in V8 engine enables arbitrary code execution when a victim visits a malicious webpage. The vulnerability is being actively exploited, requiring prompt patching of all Chromium-based browsers.
CISA KEV Yes · 2024-05-204EPSS 0.15111 (verify live)5Exploit Public PoC6CVSS 9.6 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
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
12 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-20).
Probability (EPSS)
EPSS 0.15111 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) · Affected: Google, Chromium V8. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-843 Type Confusion — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 5 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
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 type confusion in the V8 JavaScript engine.
Business
Users visiting untrusted websites face immediate risk of system compromise without warning.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the type confusion to break type safety and execute arbitrary native code within the browser process.
Business
Attackers gain full control of the browser context, enabling credential theft, malware installation, and lateral movement.
3
Lateral reach — past segmentation narrative 3
Attacker
I distribute the malicious page through ads, compromised sites, or social engineering to reach victims at scale.
Business
Organizations face widespread endpoint compromise across their user base without detection at the perimeter.
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