Google Chrome: Memory corruption in Bluetooth component
Summary
Google Chrome before 156.0.8078.47 contains a memory corruption flaw (CWE-119) in its Bluetooth component. A remote attacker can use a crafted HTML page to potentially execute arbitrary code inside the browser sandbox, but the victim must visit the page and interact with it. Code execution inside the sandbox does not by itself give full system control, and no sandbox escape is described. The upstream tracker entry describes a different bug class, so the root cause is unconfirmed.
Affected
- Google Chrome (desktop) prior to 156.0.8078.47
- Ubuntu chromium-browser packages: not affected (Chromium snap)
- Other distribution chromium packages: check the distributor advisories
Fixed in
- Google Chrome 156.0.8078.47 or later (Windows and macOS: 156.0.8078.47 or .48 or later)
- Microsoft Edge 156.0.4314.42 or later (third-party source, not verified against Microsoft)
Workaround
Not needed: a fixed version is available. Unknown whether a Chrome setting would reduce exposure without updating.
Exploitation
- No evidence of exploitation in the wild found (secondary sources only).
- No public proof of concept found.
- CISA SSVC assessment: exploitation none, automatable no, technical impact total.
- CISA KEV listing not verified directly; a third-party tracker reports no.
Our recommendation
- Inventory Chrome and Edge versions on all endpoints and confirm at least 156.0.8078.47 (156.0.8078.48 on Windows and macOS).
- Force a full browser restart, because an old process may keep running the vulnerable code.
- Check Linux chromium packages against the Debian advisories DSA 6577-1 and DLA 4853-1.
- When prioritising, note the gap between the CVSS score 8.8 and Chrome's rating Medium.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com
- Chromium issue tracker 503584859 issues.chromium.org
- NVD record via Vulners vulners.com
- Ubuntu security CVE-2026-113005 ubuntu.com
- HKCERT Microsoft Edge security bulletin www.hkcert.org
- Chrome 156 security update (CyberSecurityNews) cybersecuritynews.com
- Chrome 156 security update (WindowsForum) windowsforum.com
- VulDB entry 423068 vuldb.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 15:11.
Original description (NVD)
Memory corruption in Bluetooth in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.