Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious HTML page with WebGL exploit
-
ExploitUser visits page in Chrome browser
-
ExecutionTrigger heap buffer overflow in WebGL renderer
-
ImpactExecute arbitrary code with user privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution 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.165. Remote attacker requires no authentication. WebGL must be enabled (default configuration). Victim interaction required: opening/viewing the malicious webpage. |
| Impact | This vulnerability carries High chromium security severity and represents significant real-world risk despite missing CVSS and EPSS scores. The attack vector is Network with likely Low complexity (requires only crafted HTML), indicating broad exploitability. The technical impact permits out-of-bounds memory reads, enabling information disclosure attacks that could leak credentials, session tokens, or other sensitive data from browser memory. The absence of privilege requirement escalates risk considerably. While KEV status and active exploitation data are not provided in the intelligence sources, the High severity classification from Google's security team, combined with the public disclosure via Chrome Releases and Chromium bug tracker, suggests this is a prioritized vulnerability. The memory read capability (rather than write) slightly reduces immediate risk of remote code execution, but information disclosure from browser memory remains a critical security concern. Real-world priority is HIGH due to the large Chrome user base and the ease of delivering the exploit payload via web browsing. |
| Exploit ScenarioDerived | An attacker creates a malicious website containing WebGL code that triggers the heap buffer overflow by sending crafted graphics commands that exceed allocated buffer boundaries. When a Chrome user visits this website, the browser's renderer process executes the WebGL payload, allowing the attacker to read sensitive data from the process heap—such as cached login tokens, session data, or other in-memory secrets. The attack requires only that the victim visit the webpage and have WebGL enabled (default in modern Chrome), with no additional user interaction or privilege escalation necessary. The attacker could distribute this malicious page via social engineering, watering hole attacks, or compromised advertising networks to target specific users or conduct mass information harvesting. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 24, 2026
Google Chrome's WebGL implementation contains a heap buffer overflow that enables remote attackers to read arbitrary memory by serving a specially crafted HTML page to users prior to version 146.0.7680.165. This network-based vulnerability requires only user interaction and affects Chrome on all platforms, granting attackers access to sensitive data in the browser's memory. A patch is available and should be applied immediately given the high severity and potential for exploitation.
Earlier versions of this analysis (1)
A heap buffer overflow vulnerability exists in the WebGL implementation of Google Chrome versions prior to 146.0.7680.165, allowing remote attackers to read out-of-bounds memory through a crafted HTML page. The vulnerability affects all users of vulnerable Chrome versions across Windows, macOS, and Linux platforms. An attacker can exploit this to leak sensitive information from the browser process memory without requiring user interaction beyond visiting a malicious webpage.
RemediationAI
Upgrade Google Chrome to version 146.0.7680.165 or later immediately. Chrome will typically update automatically in the background, but users should verify their version via chrome://settings/help and restart the browser if an update is available. For enterprise environments, deploy the patched version through your managed deployment tools (Google Admin Console, Windows Group Policy, or macOS configuration profiles) as soon as possible. Until devices can be patched, restrict user access to untrusted websites and consider using security policies to limit WebGL functionality if absolutely necessary, though this may degrade web application functionality. Monitor the Chrome Releases blog (https://chromereleases.googleblog.com/) and the Chromium security issue tracker (https://issues.chromium.org/) for any updates regarding active exploitation or bypass techniques.
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
This vulnerability resides in WebGL (Web Graphics Library), a JavaScript API for rendering 2D and 3D graphics within web browsers. WebGL is implemented natively in Chromium-based browsers and interfaces with the underlying graphics drivers via OpenGL or Direct3D. The root cause, classified as CWE-122 (Heap-based Buffer Overflow), indicates that the WebGL implementation fails to properly validate buffer boundaries when processing graphics commands or shader data. An attacker crafts malicious WebGL calls that cause the renderer process to write or read beyond allocated heap memory regions. The CPE designation (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) confirms the vulnerability affects all versions of Google Chrome prior to the patched release 146.0.7680.165.
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
Heap buffer overflow in WebGL in Google Chrome prior to 146.0.7680.165 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 WebGL in Google Chrome face significant risk from CVE-2026-4675, a heap-based buffer overflow vulnerability rated CVSS 8.8. Exploitation could allow attackers to corrupt memory, crash the application, or potentially execute arbitrary code. A patch is available and should be applied as part of regular vulnerability management.
Apply vendor patch. If immediate patching is not feasible: (1) Enable ASLR and DEP where available; (2) Implement network segmentation; (3) Monitor for exploitation indicators.
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.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
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-122 – Heap-based Buffer Overflow
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-14680
GHSA-q8c9-jmgv-gvcc
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB