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-3920: Out of bounds memory access in Google Chrome

0
High
VulnerabilityCVE-2026-3920cvecve-2026-3920
Published: Wed Mar 11 2026 (03/11/2026, 22:04:05 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

CVE-2026-3920 is a high-severity vulnerability in Google Chrome prior to version 146. 0. 7680. 71 involving out-of-bounds memory access in the WebML component. This flaw allows a remote attacker to exploit heap corruption by delivering a crafted HTML page, potentially leading to full compromise of confidentiality, integrity, and availability. The vulnerability requires no privileges but does require user interaction to trigger. Although no known exploits are currently in the wild, the high CVSS score of 8. 8 indicates significant risk. Organizations using vulnerable Chrome versions are at risk of remote code execution or browser compromise. Immediate patching to version 146.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/20/2026, 02:47:54 UTC

Technical Analysis

CVE-2026-3920 is a vulnerability identified in Google Chrome's WebML component, present in versions prior to 146.0.7680.71. The flaw is characterized by an out-of-bounds memory access, which is a type of memory safety error where the program reads or writes outside the bounds of allocated memory. This specific vulnerability can be triggered remotely by an attacker who crafts a malicious HTML page that exploits the heap corruption caused by this out-of-bounds access. Heap corruption can lead to arbitrary code execution, denial of service, or data leakage. The vulnerability is classified under CWE-125 (Out-of-bounds Read) and CWE-787 (Out-of-bounds Write), indicating both read and write memory violations. The CVSS v3.1 score is 8.8 (High), reflecting that the attack vector is network-based (AV:N), requires no privileges (PR:N), but does require user interaction (UI:R). The scope is unchanged (S:U), and the impact on confidentiality, integrity, and availability is high (C:H/I:H/A:H). No public exploits have been reported yet, but the severity and ease of exploitation make it a critical patching priority. The vulnerability was published on March 11, 2026, and Google has released version 146.0.7680.71 to address it, although no direct patch links were provided in the source data.

Potential Impact

The impact of CVE-2026-3920 is significant for organizations worldwide that rely on Google Chrome as their primary web browser. Successful exploitation can lead to remote code execution within the browser context, allowing attackers to execute arbitrary code, steal sensitive data, manipulate web sessions, or disrupt browser availability. This can facilitate further network intrusion, data breaches, or deployment of malware. Since Chrome is widely used across enterprises, governments, and consumers, the vulnerability poses a broad risk surface. The requirement for user interaction means phishing or malicious web content delivery remains the primary attack vector. Organizations with high exposure to web-based threats, such as financial institutions, healthcare providers, and critical infrastructure operators, face elevated risk. Additionally, the vulnerability could be leveraged in targeted attacks against high-value individuals or entities, amplifying its potential impact.

Mitigation Recommendations

To mitigate CVE-2026-3920 effectively, organizations should immediately update all instances of Google Chrome to version 146.0.7680.71 or later, which contains the fix for this vulnerability. Beyond patching, organizations should implement strict web content filtering to block access to untrusted or suspicious websites that could host malicious HTML payloads. Deploying endpoint detection and response (EDR) solutions capable of monitoring anomalous browser behavior, especially related to WebML usage, can help detect exploitation attempts. User education on the risks of interacting with unknown or suspicious web content is critical to reduce the likelihood of triggering the vulnerability. Network segmentation and application whitelisting can further limit the impact of any successful exploitation. Finally, organizations should monitor threat intelligence feeds for any emerging exploit code or attack campaigns targeting this vulnerability to respond promptly.

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-11T05:54:09.895Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b30a512f860ef943dbd424

Added to database: 3/12/2026, 6:47:45 PM

Last enriched: 3/20/2026, 2:47:54 AM

Last updated: 4/28/2026, 7:29:00 AM

Views: 109

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