Threats / Google / CVE-2024-4671
CVE-2024-4671
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium vulnerability
Use-after-free vulnerability in Chromium's Visuals component allows remote attackers to trigger heap corruption through crafted HTML, affecting Chrome, Edge, and other Chromium-based browsers.
Verdict
Today item — known-exploited.
A use-after-free flaw in Chromium enables remote code execution via malicious web content. Active exploitation in the wild confirms practical attack viability against users of affected browsers.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
14 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-05-13).
Probability (EPSS)
EPSS 0.08348 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chromium. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious HTML page that triggers improper memory management in Chromium's rendering engine.
Business
Users visiting attacker-controlled or compromised websites face immediate risk of browser compromise and potential system access.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I host the exploit payload on a website or distribute it through social engineering to maximize victim exposure.
Business
Organizations face elevated incident response costs and potential data exfiltration from affected user endpoints.
3
Lateral reach — past segmentation narrative 3
Attacker
I achieve code execution within the browser process, bypassing sandbox protections through heap corruption.
Business
Confidentiality and integrity of user sessions, credentials, and browsing data become compromised across all Chromium-based browsers in use.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05