CVE-2026-2441: Google Chromium CSS Use-After-Free
Google Chromium · listed in the CISA catalog of actively exploited vulnerabilities since 2026-02-17.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 54%
- higher than 99% of all CVEs
- Added to CISA KEV
- 2026-02-17
- US federal due date 2026-03-10
- Ubuntu priority
- –
CVE-2026-2441 explained
CVE-2026-2441 is a use-after-free flaw in the CSS handling of Google Chromium. A crafted HTML page can let a remote attacker run arbitrary code inside the browser sandbox. It is listed in the CISA Known Exploited Vulnerabilities catalog, so systems running affected chromium builds should be updated promptly.
Impact
An attacker who gets a user to open a crafted HTML page can execute arbitrary code inside the Chromium sandbox. No privileges are needed and attack complexity is low, but user interaction is required. Successful attacks can have high impact on confidentiality, integrity and availability within the browser's context. CISA lists the flaw as known to be exploited; ransomware use is unknown.
Who is affected
The Debian source package chromium is affected. Fixed versions are available in the standard archive for all listed releases: Debian 12 (bookworm) in 145.0.7632.75-1~deb12u1, Debian 13 (trixie) in 145.0.7632.75-1~deb13u1, and Debian 14 (forky), the Debian testing distribution, in 145.0.7632.75-1. No listed release is without a fixed version.
Written with AI from the data on this page and checked against it automatically.
Official description
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)
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 145.0.7632.75
- 145.0.7632.75
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Debian 14 (forky)·chromium
testing distribution
Fixed: 145.0.7632.75-1
Debian 13 (trixie)·chromium
Fixed: 145.0.7632.75-1~deb13u1
Debian 12 (bookworm)·chromium
Fixed: 145.0.7632.75-1~deb12u1
What to do
- Update the
chromiumpackage to the fixed version for your Debian release. - On Debian 12 (bookworm), install
145.0.7632.75-1~deb12u1or later. - On Debian 13 (trixie), install
145.0.7632.75-1~deb13u1or later; on forky,145.0.7632.75-1or later. - Ask users to fully close and restart Chromium so the updated code is loaded.
- Verify the installed package version on all managed systems after the update.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace chromium with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-416 Use after free
Questions about CVE-2026-2441
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2026-2441 to its Known Exploited Vulnerabilities catalog on 2026-02-17, with a US federal due date of 2026-03-10. Whether it is used in ransomware campaigns is unknown.
- Does updating the package protect running browsers immediately?
- No. Chromium processes that were started before the update keep running the old code. Users must close and restart the browser for the fix to take effect.
- Can an attacker take over the whole system?
- The description states code execution happens inside the sandbox. It requires a user to open a crafted HTML page. The facts do not state that the sandbox can be escaped.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.