How severe is CVE-2026-2441?

CVE-2026-2441 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-2441?

Affected package information for CVE-2026-2441 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-2441?

No fixed version has been published for CVE-2026-2441 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2026-2441 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2026-2441, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2026-2441?

CVE-2026-2441 has an EPSS (Exploit Prediction Scoring System) score of 23.1%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2026-2441 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-2441 (Google Chromium CSS Use-After-Free Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-02-17. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-03-10. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-2441?

CVE-2026-2441 is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-2441 published, and has it been updated?

CVE-2026-2441 was published on February 13, 2026 and was last updated on March 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-02-17 — agencies required to remediate by 2026-03-10

CVE-2026-2441

HIGH

Published

Feb 13, 2026

Updated

Mar 23, 2026

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

23.1%probability of exploitation in next 30 days

Moderate Risk96th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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)

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52542localmultiple

Google Chrome 145.0.7632.75 - CSSFontFeatureValuesMap

by nu11secur1ty · Apr 30, 2026

Exploit-DB Source

Frequently Asked Questions

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)

O3 Security · Impact-Aware SCA

Is CVE-2026-2441 in your stack?

O3 detects CVE-2026-2441 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works