CVE-2024-4671

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)

CVSS: 9.6Criticalscored by CISA
Exploited in the wild: Yes, in CISA KEV since 13 May 2024CISA deadline for US federal agencies: 3 Jun 2024
EPSS: 8.3%chance of exploitation in the next 30 daystop 5% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 14 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

Attack surface: Server-side
Exploitable: At runtime
Attack vector: network
Weakness: CWE-416 Use After Free

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

Product	Affected versions	Vendor says fixed in
Google Chrome	< 124.0.6367.201Vendor says fixed in: not stated	Not stated by the vendor

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 vulnerability is triggered by a crafted HTML page loaded in the browser, which is delivered via HTTP. The malicious input looks like a normal web page, so a web application firewall cannot reliably distinguish it from legitimate traffic.

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 13 May 2024.
CISA due date: 3 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: None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC: exploitation active, automatable no, technical impact totalAssessed by CISA 14 May 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

13 May 2024Added to CISA KEV (exploited in the wild)
14 May 2024CISA SSVC assessment: exploitation active1 day later
14 May 2024Publishedsame day later
3 Jun 2024CISA remediation due date (US federal agencies)19 days later
21 Oct 2025CVE record last updated506 days (about 1 year) later
12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

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

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	RequiredA victim must click, open or otherwise cooperate.	A victim must click, open or otherwise cooperate.
Scope	ChangedImpact crosses a security boundary into other components.	Impact crosses a security boundary into other components.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	HighComplete modification possible.	Complete modification possible.
Availability	HighFull outage possible.	Full outage possible.

Common questions

Is CVE-2024-4671 being exploited?

Yes. CVE-2024-4671 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-4671?

CVE-2024-4671 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-4671?

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

What does CVE-2024-4671 affect?

CVE-2024-4671 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

NVD CVE.org CVE Details Source

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

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile

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.