⚠ Known Exploited Vulnerability (KEV) Tracker

Description

Google Chromium V8 contains a type confusion vulnerability that allows a remote attacker to execute code via a crafted HTML page.

Lifecycle Timeline

• 2024-05-15
  CVE published

  Entered the public CVE record.

  CVE.org →
• 2024-05-16
  First national advisory 1 day later

  CERT-EU — 2024-044: Zero-day Vulnerability in Chrome

  CyberzSOC advisory index →
• 2024-05-20
  Added to CISA KEV 4 days later

  Listed as known exploited, which starts the federal remediation clock.

  CISA KEV →
• 2024-06-10
  Federal remediation due 21 days later

  Deadline for federal civilian agencies under BOD 22-01 — now passed.

  CISA KEV
• 2025-07-21
  Public exploit code 13 months later

  Public GitHub repository bjrjk/CVE-2024-4947 — unvetted, may contain malware

  GitHub PoC →
• not recorded
  EPSS flags exploitation risk

  Reached 10% only through a model recalibration, which moves every score at once and says nothing about this CVE.
• not recorded
  Vendor fix published

  No dated vendor fix. Only Microsoft publishes a machine-readable release date; other vendors state a fixed version without one.

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 135 points from 2024-05-18, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 23.5% on 2025-03-29.

Published Applicability

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Research & News Coverage

No mentions found in monitored research blogs or news feeds.

Detection & Exploitation

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB and public GitHub repositories (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and are not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

Distribution Status

Where the distribution has shipped a fix, and in which version. Green means the release has resolved it, amber that it is still open. Data from the Debian Security Tracker, used under Debian's MIT / GPLv2+ terms. Debian is upstream of several other distributions, so a fix here often precedes theirs.

CISA Assessment (Vulnrichment / SSVC)

KEV Catalog Status

Listed By

Referenced in Advisories

Weaponization Timeline — Offensive & Testing Tools

No exploit-tool sightings recorded for this CVE.

Evidence tiers are explained on the About page — a merged Metasploit module is far stronger evidence than a distro package mention.

External References

CVE.org record → NVD entry → CISA KEV catalog → FortiGuard Labs → Rapid7 AttackerKB →