Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious HTML page
-
DeliveryUser visits page in Chrome browser
-
ExploitTrigger out of bounds read in Blink renderer
-
ExecutionRead sensitive memory
-
ImpactLeak confidential data or escalate privileges
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 a crafted HTML page in Google Chrome versions prior to 146.0.7680.153. Remote unauthenticated attacker can deliver via malicious website or email link. No special Chrome configuration required; default installations are vulnerable. |
| Impact | While CVSS score and vector data are not provided, the Chromium security classification of 'High' and the CWE-125 designation indicate significant real-world risk. The attack vector is network-based (via crafted HTML pages), attack complexity is low (standard web delivery), and no user privileges are required—making this trivial to exploit at scale. The vulnerability enables information disclosure, potentially leaking sensitive data from the renderer process memory (encryption keys, authentication tokens, browsing history). The absence of CVSS data and EPSS metrics limits quantitative risk scoring, but the combination of high vendor severity, low attack complexity, widespread Debian tracking, and availability of vendor patches suggests this is a genuine priority requiring rapid patching rather than a low-real-risk high-CVSS case. The patch's public availability and advisory presence indicate coordinated disclosure without evidence of active wild exploitation at announcement time. |
| Exploit ScenarioDerived | An attacker hosts a malicious website containing crafted HTML markup that triggers the out of bounds read in Blink's buffer handling logic. When a victim visits the site using a vulnerable Chrome version, the renderer process reads memory beyond intended buffer boundaries, exfiltrating sensitive data (e.g., cached credentials, cryptographic material) back to the attacker's server via WebSocket or fetch API calls. No user interaction beyond page load is required, and the low attack complexity means the exploit can be delivered at scale through ad networks, compromised legitimate websites, or spear-phishing campaigns. The vulnerability's information disclosure nature makes it particularly valuable as a reconnaissance vector for multi-stage attacks targeting Chrome's sandbox or system-level exploits. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 20, 2026
An out of bounds read vulnerability exists in the Blink rendering engine of Google Chrome prior to version 146.0.7680.153, allowing remote attackers to read memory outside intended buffer boundaries via a specially crafted HTML page. This vulnerability (CWE-125) has been classified as High severity by the Chromium security team and enables information disclosure attacks without requiring user interaction beyond visiting a malicious webpage. A vendor patch is available, and the vulnerability affects 9 Debian releases, indicating widespread downstream impact across Linux distributions.
RemediationAI
Immediately upgrade Google Chrome to version 146.0.7680.153 or later via the built-in auto-update mechanism (Settings > About > Google Chrome) or manual download from https://www.google.com/chrome/. For Debian-based systems, update the chromium or google-chrome package using apt-get update && apt-get install google-chrome-stable or equivalent package manager commands once security updates are released to the Debian repositories. Until patching is feasible in constrained environments, restrict browser usage to trusted websites only, disable JavaScript execution for untrusted content via browser extensions (uBlock Origin, NoScript), and enforce Content Security Policy (CSP) headers on internal applications to limit attack surface. Consider deploying sandboxing solutions or containerized browser environments for high-risk user populations.
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 Blink, Google Chrome's open-source web rendering engine derived from WebKit, which is responsible for parsing and rendering HTML, CSS, and executing JavaScript. CWE-125 (Out-of-bounds Read) indicates that the vulnerability occurs when the Blink parser or related memory-handling code fails to properly validate buffer boundaries, permitting an attacker to read adjacent memory regions beyond the allocated buffer. The affected component processes untrusted HTML input directly from web pages, making the attack surface trivial to reach. The vulnerability was discovered through Chromium's issue tracker (issues.chromium.org/issues/491080830) and impacts the stable release channel across Windows, macOS, and Linux platforms.
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 Blink in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Organizations using Blink in Google Chrome face significant risk from CVE-2026-4462, 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 146.0.7680.153 Memory Corruption
View all 26Use-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
Ubuntu
Priority: Medium| Release | Status | Version |
|---|---|---|
| jammy | not-affected | code not present |
| noble | not-affected | code not present |
| questing | not-affected | code not present |
| upstream | released | - |
Debian
| Release | Status | Fixed Version | Urgency |
|---|---|---|---|
| bullseye (security), bullseye | vulnerable | 120.0.6099.224-1~deb11u1 | - |
| bookworm | fixed | 146.0.7680.153-1~deb12u1 | - |
| bookworm (security) | fixed | 146.0.7680.153-1~deb12u1 | - |
| trixie | fixed | 146.0.7680.153-1~deb13u1 | - |
| trixie (security) | fixed | 146.0.7680.153-1~deb13u1 | - |
| forky | vulnerable | 146.0.7680.80-1 | - |
| sid | fixed | 146.0.7680.153-1 | - |
| bullseye | fixed | (unfixed) | end-of-life |
| (unstable) | fixed | 146.0.7680.153-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-13479
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB