Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-4675: Heap buffer overflow in Google Chrome

0
High
VulnerabilityCVE-2026-4675cvecve-2026-4675
Published: Tue Mar 24 2026 (03/24/2026, 00:24:41 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

CVE-2026-4675 is a high-severity heap buffer overflow vulnerability in the WebGL component of Google Chrome versions prior to 146. 0. 7680. 165. It allows a remote attacker to trigger an out-of-bounds memory read by delivering a crafted HTML page, potentially leading to full compromise of confidentiality, integrity, and availability. Exploitation requires user interaction but no privileges or authentication. Although no known exploits are currently observed in the wild, the vulnerability's high CVSS score of 8. 8 reflects its critical impact. This flaw affects a widely used browser, making it a significant risk for organizations globally. Mitigation involves promptly updating Chrome to version 146.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/31/2026, 20:29:26 UTC

Technical Analysis

CVE-2026-4675 is a heap buffer overflow vulnerability discovered in the WebGL implementation of Google Chrome prior to version 146.0.7680.165. WebGL is a web standard that enables rendering interactive 3D graphics within browsers using the GPU. The vulnerability arises from improper bounds checking during memory operations, allowing a remote attacker to perform an out-of-bounds read on the heap memory. This can lead to information disclosure, memory corruption, and potentially arbitrary code execution. The attack vector is remote and requires only that a user visits a maliciously crafted HTML page containing WebGL content designed to exploit this flaw. No privileges or authentication are required, but user interaction (visiting the page) is necessary. The vulnerability has a CVSS v3.1 base score of 8.8, reflecting high impact on confidentiality, integrity, and availability. Although no public exploits have been reported yet, the nature of the flaw and the ubiquity of Chrome make it a critical security concern. Google has addressed the issue in Chrome version 146.0.7680.165, but users running older versions remain vulnerable. The flaw could be leveraged by attackers to execute arbitrary code, steal sensitive information, or cause browser crashes, impacting end users and enterprise environments alike.

Potential Impact

The impact of CVE-2026-4675 is significant due to the widespread use of Google Chrome as a primary web browser globally. Successful exploitation can lead to remote code execution, enabling attackers to take full control of the affected system under the context of the browser user. This compromises confidentiality by exposing sensitive data, integrity by allowing unauthorized code execution, and availability by causing browser or system crashes. Organizations relying on Chrome for daily operations, especially those handling sensitive information or operating in high-risk sectors such as finance, healthcare, and government, face elevated risks. The vulnerability could be exploited to deploy malware, conduct espionage, or disrupt services. Given the ease of exploitation (no privileges required and only user interaction), the threat surface is broad, affecting individual users, enterprises, and cloud environments where Chrome is used for web access. The absence of known exploits in the wild currently provides a window for proactive mitigation before active exploitation occurs.

Mitigation Recommendations

To mitigate CVE-2026-4675, organizations and users should immediately update Google Chrome to version 146.0.7680.165 or later, where the vulnerability is patched. Enterprises should enforce browser update policies and automate patch management to ensure timely deployment. Additionally, restricting access to untrusted or unknown websites can reduce exposure, as exploitation requires visiting a malicious page. Employing web content filtering and network security controls to block or monitor suspicious WebGL activity can provide additional defense layers. Security teams should monitor threat intelligence feeds for any emerging exploit attempts targeting this vulnerability. For high-security environments, consider disabling WebGL functionality temporarily until patches are applied. User education on avoiding suspicious links and websites also helps reduce risk. Finally, integrating browser security features such as sandboxing and enabling exploit mitigation technologies can limit the impact of potential attacks.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Chrome
Date Reserved
2026-03-23T21:08:17.405Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69c1debff4197a8e3babf885

Added to database: 3/24/2026, 12:45:51 AM

Last enriched: 3/31/2026, 8:29:26 PM

Last updated: 5/7/2026, 5:03:02 AM

Views: 193

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses