Threats / Google / CVE-2026-2441
CVE-2026-2441
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium vulnerability
Use-after-free vulnerability in Chromium CSS processing allows remote code execution through crafted HTML, affecting Chrome, Edge, and Opera browsers.
Verdict
Today item — known-exploited.
A use-after-free flaw in CSS handling enables heap corruption when processing malicious web pages. Attackers can exploit this remotely without user interaction beyond visiting a compromised site, leading to arbitrary code execution in the browser context.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
4 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 2026-02-17).
Probability (EPSS)
EPSS 0.2202 — 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 with CSS that triggers the use-after-free condition in the browser's rendering engine.
Business
Users visiting attacker-controlled or compromised websites face arbitrary code execution within browser privileges, risking credential theft and system compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I host the exploit page on a website or inject it into legitimate sites via watering hole attacks to maximize victim exposure.
Business
Organizations lose visibility and control over employee browsing security, with potential lateral movement into corporate networks from compromised endpoints.
3
Lateral reach — past segmentation narrative 3
Attacker
I use the code execution to install malware, steal session tokens, or establish persistence on affected systems.
Business
Data breaches, credential compromise, and malware distribution create regulatory liability and reputational damage across affected user bases.
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