Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Out-of-bounds read in Google Chrome CSS

IdentifiersCVE-2026-4674CWE-125· Out-of-bounds Read

CVE-2026-4674 is a high-severity out-of-bounds read vulnerability in the CSS component of Google Chrome. It affects Google Chrome versions prior to 146.0.7680.165. According to the provided content, a remote attacker can trigger out-of-bounds memory access by causing a target to load a crafted HTML page that exercises the vulnerable CSS handling path. The available information does not identify the specific vulnerable function, but the flaw is characterized as an out-of-bounds read during CSS processing.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to cause out-of-bounds memory access in the browser process. Based on the provided content and associated CVSS metadata, impact may include disclosure of sensitive memory contents, browser instability or denial of service, and potentially contribution to further exploitation chains. The broader Chrome update context notes that high-severity browser flaws of this class may enable code execution or security bypass in some scenarios, but the specific confirmed impact for this CVE in the provided material is out-of-bounds memory read via crafted HTML content.

Mitigation

If you can’t patch tonight, do this now.

Apply the vendor update as the primary mitigation. Until patching is complete, reduce exposure by limiting access to untrusted or attacker-controlled websites and HTML content, and ensure users restart Chrome after the update is installed because protections do not become active until relaunch. In enterprise environments, prioritize rapid rollout of the fixed Chrome version.

Remediation

Patch, then assume compromise.

Update Google Chrome to version 146.0.7680.165 or later. The provided content states that versions prior to 146.0.7680.165 are affected. For managed environments, deploy the corresponding stable-channel update through enterprise patch management processes and ensure browsers are restarted so the fix takes effect.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.