Skip to main content
VulnerabilityPublished

CVE-2026-3916: Google Chrome · Out-of-bounds Read

Affects Google ChromeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.6 Critical : upgrade to 146.0.7680.71 as a priority.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 146.0.7680.71
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Google Chrome to 146.0.7680.71.

Affected software

ProductAffectedFixed in
GoogleChromeAffected
  • >=146.0.7680.71 <146.0.7680.71
Fixed in
  • 146.0.7680.71

AI-suggested

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.

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)

References

Community reviews

Loading reviews…