Cyber Resilience

CVE-2026-2441

Memory Safety in Google Chrome ≤ 145.0.7632.75

CISA KEVActive ExploitationEUVD ExploitedPublic PoCMemory Safety
Published
13 February 2026
Modified
23 February 2026
KEV Added
17 February 2026
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.22 97th percentile
Risk Priority 90 floored blend · peak EPSS

Summary

CVE-2026-2441 is a high-severity Use After Free (CWE-416) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked in the top 3% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-2441 is a use-after-free vulnerability (CWE-416) in the CSS component of Google Chrome prior to version 145.0.7632.75. Published on 2026-02-13, it carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and Chromium security severity of High.

A remote attacker can exploit this vulnerability by crafting an HTML page that triggers the use-after-free, enabling arbitrary code execution inside the browser's sandbox. Exploitation requires user interaction, such as visiting a malicious site, but needs no privileges or special access.

Mitigation involves updating to Google Chrome 145.0.7632.75 or later, as announced in the stable channel update on the Chrome Releases blog (chromereleases.googleblog.com/2026/02/stable-channel-update-for-desktop_13.html). Additional details are in the Chromium issue tracker (issues.chromium.org/issues/483569511), and a proof-of-concept is publicly available on GitHub (github.com/huseyinstif/CVE-2026-2441-PoC/blob/main/poc.html).

The vulnerability appears in CISA's Known Exploited Vulnerabilities Catalog (cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-2441), signaling real-world exploitation.

EU & UK References

Vulnerability Data

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)

CWE(s)
CWE-416
KEV Date Added
17 February 2026

Related Threats

MITRE ATT&CK Enterprise Techniques

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-5281Same product: Apple Macosboth on KEV
CVE-2026-11152Same product: Apple Macos
CVE-2026-10909Same product: Apple Macos
CVE-2026-11049Same product: Apple Macos
CVE-2026-11700Same product: Apple Macos
CVE-2026-3922Same product: Apple Macos
CVE-2026-7342Same product: Apple Macos
CVE-2026-10919Same product: Apple Macos
CVE-2026-10884Same product: Apple Macos
CVE-2026-11125Same product: Apple Macos

Affected Assets

google
chrome
≤ 145.0.7632.75 · ≤ 145.0.7632.76

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.4.3

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover use-after-free bugs through dynamic analysis or fuzzing.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require memory-safe constructs or languages that structurally avoid introducing use-after-free.

SC-39 Process Isolation partial match

Process isolation confines the blast radius of use-after-free memory corruption to a single execution domain.

SI-16 Memory Protection partial match

Memory protection controls limit exploitation impact by blocking unauthorized code execution from dangling pointers.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly incorporate memory-safety tooling and reviews that prevent most use-after-free defects.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover use-after-free issues via scanning or analysis but do not prevent their introduction.

PR.PS-02 partial match
prevents

Routine patching removes known use-after-free instances after they have been introduced in released software.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect use-after-free bugs before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates memory-safety practices that reduce use-after-free defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-management rules that mitigate use-after-free.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include memory-safety design choices that limit use-after-free exposure.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prescribe avoidance of use-after-free patterns.

A.8.32 Change management partial match
prevents

Change-management processes help ensure memory-safety fixes are deployed consistently.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248592 OL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416
RHEL 8 (1 rule)
  • V-230279 RHEL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416
RHEL 9 (1 rule)
  • V-257794 RHEL 9 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416

References