Skip to content

CVE-2024-4947

Type Confusion in V8 in Google Chrome prior to 125.0.6422.60 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS
9.6Criticalscored by CISA
Exploited in the wild
Yes, in CISA KEV since 20 May 2024CISA deadline for US federal agencies: 10 Jun 2024unvetted proof-of-concept code on github
EPSS
15.2%chance of exploitation in the next 30 daystop 4% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
15 May 2024analysed here 12 Nov 2026

Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable
At runtime
Attack vector
network
Weakness

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Google Chrome< 125.0.6422.60Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • google:chrome
  • fedoraproject:fedora

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack is delivered via a crafted HTML page loaded in the browser, which looks like a normal web page request. The malicious input is embedded in the page content, making it indistinguishable from legitimate web traffic to a web application firewall.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 20 May 2024.
CISA due date
10 Jun 2024, the remediation deadline for US federal agencies
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploit code
Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept
CISA SSVC
exploitation active, automatable no, technical impact totalAssessed by CISA 23 May 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 15 May 2024Published
  2. 20 May 2024Added to CISA KEV (exploited in the wild)4 days later
  3. 23 May 2024CISA SSVC assessment: exploitation active4 days later
  4. 10 Jun 2024CISA remediation due date (US federal agencies)17 days later
  5. 21 Jul 2025First proof-of-concept repository on GitHub (unvetted)406 days (about 1 year) later
  6. 16 Dec 2025CVE record last updated149 days (about 5 months) later
  7. 12 Nov 2026Analysed by vulneraibility.com331 days (about 11 months) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionRequiredA victim must click, open or otherwise cooperate.
ScopeChangedImpact crosses a security boundary into other components.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2024-4947 being exploited?

Yes. CVE-2024-4947 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-4947?

CVE-2024-4947 is rated Critical with a CVSS score of 9.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-4947?

Yes. A fix has been recorded for CVE-2024-4947. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-4947 affect?

CVE-2024-4947 affects google:chrome, fedoraproject:fedora. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

6 references in the CVE record, grouped by the tags the record gives them.

Other links (6)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com