What is CVE-2026-2441?
Use after free in CSS in Google Chrome prior to 145.0.7632.75 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
The record classifies CVE-2026-2441 under weakness class CWE-416. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 4 affected-product entries are recorded, across 4 vendors, listed below. The identifier was first published 234 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 8.8 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 0.2% probability of exploitation in the next 30 days, higher than 49.4% of all scored CVEs
- CISA KEV
- Listed since 2026-02-17, federal remediation deadline 2026-03-10
- Threadlinqs priority
- 9/10 — CISA KEV-listed, which Threadlinqs floors at 9
- Published
- 2026-02-13, last modified 2026-02-23
Is CVE-2026-2441 being exploited?
CISA added CVE-2026-2441 to the Known Exploited Vulnerabilities catalog on 2026-02-17, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2026-03-10 under BOD 22-01. It currently carries a trending score of 27 in the Threadlinqs vulnerability feed.
Affected products and versions
How to fix CVE-2026-2441
Because CVE-2026-2441 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2026-03-10. No vendor patch reference has been recorded for CVE-2026-2441 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-2441
1 tracked threat in the Threadlinqs corpus references CVE-2026-2441, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Seeded from nvd and not yet processed by the Threadlinqs enrichment pipeline, so blank CVSS, EPSS or KEV fields above mean NOT MEASURED rather than measured-absent.