Live › vulnerability › CVE-2026-113310
Go to dashboardA flaw in Chrome's Bluetooth code lets a crafted HTML page read memory outside an intended buffer, but only inside the browser sandbox. An attacker gets information from the browser process memory space, not direct code execution from the page alone.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Any machine running Google Chrome before is exposed when a user visits an attacker-controlled page. Teams that only use Chrome on managed fleets with automatic updates are usually patched quickly, and servers without a browser are not affected.
156.0.8078.47| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| google chrome | vendor | < 156.0.8078.47 | 156.0.8078.47 |
chrome://version in Google Chrome and compare the version with 156.0.8078.47156.0.8078.47 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Out of bounds read in Bluetooth in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: High)
This page as .md · .json · in your agent: get_signal("CVE-2026-113310")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.