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-3916: Out of bounds read in Google Chrome

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

Description

Out of bounds read in Web Speech in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

AI-Powered Analysis

AILast updated: 03/12/2026, 18:53:47 UTC

Technical Analysis

CVE-2026-3916 is an out-of-bounds read vulnerability discovered in the Web Speech component of Google Chrome prior to version 146.0.7680.71. This vulnerability arises when the browser improperly handles memory boundaries while processing Web Speech API data, leading to an out-of-bounds read condition. Exploiting this flaw, a remote attacker can craft a malicious HTML page that triggers the vulnerability, potentially enabling a sandbox escape. Sandbox escapes are critical because they allow attackers to break out of the browser's restricted execution environment, potentially gaining access to the underlying operating system or other sensitive resources. Although no public exploits have been reported yet, the Chromium security team has classified this vulnerability as high severity due to the risk of privilege escalation and system compromise. The vulnerability affects all platforms running the vulnerable Chrome versions, including Windows, macOS, Linux, and Chrome OS. The lack of a CVSS score indicates the need for a manual severity assessment, considering the impact on confidentiality, integrity, and availability, the ease of exploitation (remote, no authentication required), and the widespread use of Chrome worldwide. The vulnerability was publicly disclosed on March 11, 2026, and users are urged to update to the patched version 146.0.7680.71 or later to mitigate the risk.

Potential Impact

The primary impact of CVE-2026-3916 is the potential for a remote attacker to escape the Chrome sandbox via a crafted HTML page exploiting the out-of-bounds read in the Web Speech component. This can lead to unauthorized access to system resources beyond the browser sandbox, potentially allowing execution of arbitrary code with elevated privileges. Such a compromise can result in data theft, installation of persistent malware, or further lateral movement within a network. Given Chrome's dominant market share as a web browser, the vulnerability affects a vast number of users and organizations globally, increasing the risk of widespread exploitation once public exploits emerge. The attack requires only that a user visit a malicious or compromised website, making it highly accessible to attackers. This vulnerability threatens confidentiality by exposing sensitive data, integrity by enabling unauthorized code execution, and availability by potentially causing system instability or denial of service. Organizations relying on Chrome for daily operations, especially those handling sensitive or regulated data, face significant risk if unpatched.

Mitigation Recommendations

To mitigate CVE-2026-3916, organizations and users should immediately update Google Chrome to version 146.0.7680.71 or later, where the vulnerability is patched. Beyond patching, organizations should implement network-level protections such as web filtering to block access to known malicious sites and employ endpoint detection and response (EDR) tools to monitor for suspicious browser behavior indicative of sandbox escapes. Employing browser hardening techniques, such as disabling unnecessary Web Speech API features if not required, can reduce the attack surface. Security teams should also conduct user awareness training to recognize phishing and malicious web content risks. Regularly auditing and restricting browser extensions can prevent additional exploitation vectors. In high-security environments, consider deploying application sandboxing or containerization technologies to further isolate browser processes. Continuous monitoring of threat intelligence feeds for any emerging exploit code targeting this vulnerability is recommended to enable rapid response.

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:08.667Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69b30a512f860ef943dbd42c

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

Last enriched: 3/12/2026, 6:53:47 PM

Last updated: 3/13/2026, 8:16:45 AM

Views: 7

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 in Console -> Billing 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