CVE-2024-4947 · Published 15 May 2024
Google Chromium V8
On CISA's KEV list 5 days after disclosure; 3 public exploits.
Google Chromium V8 contains a type confusion vulnerability that allows a remote attacker to execute code via a crafted HTML page.
CISA required action (federal due date 10 Jun 2024): Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Signals
- KEV, exploited in the wild
- yes, added 20 May 2024, due 10 Jun 2024
- EPSS, 30-day forecast
- 15%, 97th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.
Timeline 15 May 2024 to today
- Disclosed
- KEV+5 d
- First PoC+427 d
427 days from the KEV listing to the first proof of concept
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 0 dispatches
No dispatch on our wire has named this CVE yet.
Public exploit code 3 known · links only
GitHub PoCs 3Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars3
- bjrjk/CVE-2024-4947Trust ok 10032 stars
A in-the-wild V8 type confusion bug.
created 21 Jul 2025
- l1m3syc/CVE-2024-4947-PoCTrust ok 1000 stars
created 20 Aug 2026
- uixss/PoC-CVE-2024-4947Not checked
first seen by skopnix 18 Oct 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.