Skip to main content
CVE-2024-4671VulnerabilityPublished Updated

CVE-2024-4671: Google Chrome · Use after free

Affects Google ChromeSource CVE Database V5

0

Exploited in the wild · KEV due 3 Jun 2024 · 8% EPSS : upgrade to 124.0.6367.201 now.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS
8.3% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 124.0.6367.201
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 9 May 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: evidence found.

    Listed in CISA KEV 4 days after disclosure

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Chrome

    , 21 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. , 4 days after disclosure

  4. KEV remediation due

    US federal deadline

    , 25 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade google/chrome to 124.0.6367.201.

Affected software

ProductAffectedFixed in
Googlegoogle/chromepkg:deb/google/chromeOther threatsAffected
  • <124.0.6367.201
Fixed in
  • 124.0.6367.201

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Use after free in Visuals in Google Chrome prior to 124.0.6367.201 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

References

Community reviews

Loading reviews…