Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious HTML with CSS exploit
-
DeliveryLoad page in Chrome browser
-
ExploitTrigger out-of-bounds read in CSS parser
-
ExecutionAccess adjacent memory regions
-
ImpactLeak sensitive data or corrupt memory
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The victim must open or visit a crafted HTML page in Google Chrome prior to version 146.0.7680.165. No authentication required. Remote attacker delivers malicious HTML containing out-of-bounds CSS code. |
| Impact | This vulnerability presents a moderate-to-high real-world risk despite the absence of a publicly disclosed CVSS vector and EPSS score. The attack vector is Network (AV:N) and requires no user interaction beyond visiting a malicious webpage, making it easily exploitable at scale. The attack complexity is likely Low (AC:L), as the attacker only needs to serve a crafted HTML page; no special privileges or authentication are required. The technical impact is Information Disclosure (C:H, I:N, A:N), allowing memory leaks but not code execution or system compromise. Chromium's High severity classification aligns with the exploitability: this is a remote, zero-interaction vulnerability that can leak sensitive information. The absence of reported active exploitation (KEV status unknown from provided data) and lack of public proof-of-concept code reduce immediate threat, but the ease of weaponization and broad Chrome user base (billions of users) warrant prompt patching. Organizations should prioritize this as a medium priority for patch deployment within 30 days, higher for high-value targets or users in environments where memory contents may contain secrets. |
| Exploit ScenarioDerived | An attacker hosts a malicious website containing a crafted HTML page with specially-formatted CSS rules designed to trigger an out-of-bounds read in Chrome's CSS parser. When a victim visits the site (through phishing, watering hole, or organic discovery), the browser automatically parses the malicious CSS, causing the parser to read memory beyond the intended buffer boundaries. The attacker can then exfiltrate the leaked memory contents via JavaScript to reveal heap layout information, encryption keys, or other sensitive data stored in the Chrome process memory. Since the attack requires only network delivery of a webpage and no user interaction beyond browsing, it is practical for mass exploitation campaigns targeting Chrome users. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 24, 2026
Out of bounds memory read in Google Chrome's CSS parser prior to version 146.0.7680.165 allows remote attackers to access sensitive memory contents through a malicious HTML page. The vulnerability requires user interaction and affects Chrome on multiple platforms including Debian systems, enabling attackers to potentially leak confidential data with high impact on confidentiality and integrity.
Earlier versions of this analysis (1)
An out-of-bounds read vulnerability exists in the CSS processing engine of Google Chrome prior to version 146.0.7680.165, allowing remote attackers to read memory beyond allocated buffer boundaries. Affected users running vulnerable Chrome versions on all platforms can be exploited through a crafted HTML page served over the network, potentially leading to information disclosure of sensitive memory contents. This vulnerability is classified as High severity by Chromium and assigned CWE-125 (Out-of-Bounds Read), though no active exploitation in the wild or public proof-of-concept has been reported at this time.
RemediationAI
Immediately upgrade Google Chrome to version 146.0.7680.165 or later via the built-in auto-update mechanism (Settings > About Chrome), which will automatically download and apply the patch on the next browser restart. For enterprise environments, deploy the patched version via managed software distribution (Windows: Group Policy or SCCM; macOS: Jamf or similar MDM; Linux: package manager updates). Until patching is complete, mitigate risk by restricting user browsing to trusted, curated websites and disabling JavaScript execution for untrusted origins via browser extensions or corporate proxy policies. Additionally, monitor Chrome user populations for successful updates and enforce a compliance deadline for all users within 7 days. The official patch and technical details are available via the Chromium issue tracker at https://issues.chromium.org/issues/488188166 and the Chrome Releases blog at https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_23.html.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in Google Chrome's CSS (Cascading Style Sheets) rendering and parsing subsystem, which is responsible for interpreting stylesheet rules and applying visual formatting to web documents. CWE-125 identifies this as a classic out-of-bounds read condition, where the CSS parser attempts to access memory at an index or offset that exceeds the bounds of an allocated buffer or array. This type of flaw typically occurs due to insufficient bounds checking during string parsing, array indexing, or pointer arithmetic in the CSS tokenizer or property value parser. The affected product is Google Chrome across all platforms (Windows, macOS, Linux, and Chrome OS), as indicated by the CPE string cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, which encompasses all versions prior to the patched release 146.0.7680.165. Attackers exploit this by crafting malicious CSS declarations or selectors that trigger the out-of-bounds condition when parsed, allowing arbitrary memory reads that can disclose heap contents, internal data structures, or other sensitive information.
Know when Chrome gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
Out of bounds read in CSS in Google Chrome prior to 146.0.7680.165 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Organizations using CSS in Google Chrome face significant risk from CVE-2026-4674, a out-of-bounds read vulnerability rated CVSS 8.8. Successful exploitation could significantly impact the confidentiality, integrity, or availability of affected systems. A patch is available and should be applied as part of regular vulnerability management.
Apply vendor patch. If immediate patching is not feasible: (1) Implement network-level access controls to limit exposure; (2) Enable enhanced monitoring and alerting; (3) Apply principle of least privilege.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in Google Chrome Memory Safety Vulnerabilities
View all 7Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13
Same weakness CWE-125 – Out-of-bounds Read
View allSame technique Buffer Overflow
View allVendor StatusVendor
Debian
| Release | Status | Fixed Version | Urgency |
|---|---|---|---|
| bullseye (security), bullseye | vulnerable | 120.0.6099.224-1~deb11u1 | - |
| bookworm | vulnerable | 143.0.7499.169-1~deb12u1 | - |
| bookworm (security) | vulnerable | 146.0.7680.153-1~deb12u1 | - |
| trixie | vulnerable | 145.0.7632.159-1~deb13u1 | - |
| trixie (security) | vulnerable | 146.0.7680.153-1~deb13u1 | - |
| forky | vulnerable | 146.0.7680.153-1 | - |
| sid | fixed | 146.0.7680.164-1 | - |
| bullseye | fixed | (unfixed) | end-of-life |
| (unstable) | fixed | 146.0.7680.164-1 | - |
SUSE
Severity: High| Product | Status |
|---|---|
| SUSE Package Hub 15 SP6 | Fixed |
| openSUSE Leap 15.6 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP6 | Fixed |
EUVD-2026-14678
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB