EUVD-2026-89378
GHSA-3f6r-r54x-cfvh
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryTrigger Bluetooth use-after-free in Chrome
-
ExploitReclaim freed object, corrupt memory
-
ExecutionEscape renderer sandbox
-
ImpactExecute arbitrary code on host
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a victim running Google Chrome prior to 154.0.8037.92 to load attacker-controlled HTML that exercises the Web Bluetooth code path (UI:R - user must navigate to the crafted page). No authentication is needed (PR:N) and no special server-side configuration is required, but the crafted page must be able to reach and manipulate the Bluetooth subsystem to trigger the use-after-free. The primary limiting factors are the user-interaction requirement (visiting the page) and the need for the target to be on a vulnerable, unpatched Chrome build; the scope change (S:C) reflects that successful exploitation can break out of the browser sandbox. |
| Impact | This is a genuinely high-priority vulnerability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, score 9.6) describes a network-reachable, low-complexity, unauthenticated flaw requiring only that a victim visit a page, with a scope change reflecting the fact that the description explicitly states code execution occurs OUTSIDE the Chrome sandbox - this is a sandbox-escape-class RCE rather than a renderer-contained bug, which is what pushes the score to 9.6. All three impact metrics are High. No EPSS score was supplied and the CVE is not listed in CISA KEV, so there is no public signal of active exploitation, and no public exploit code was identified. The high CVSS is credible here (not inflated) because Google/Chromium confirmed the UAF and the out-of-sandbox execution potential. The main tempering factor is UI:R - a user must open a crafted page - but for a browser that is a routine, low-friction condition. Given Chrome's ubiquity and Chromium's history of n-day exploitation once patches reveal the bug, patching should be treated as urgent even absent KEV/EPSS data. |
| Exploit ScenarioDerived | An attacker hosts or injects a crafted HTML page that drives Chrome's Bluetooth subsystem into a use-after-free state; when a victim on an unpatched build (prior to 154.0.8037.92) visits the page, the freed object is reclaimed and manipulated to corrupt memory. Because the flaw can lead to execution outside the renderer sandbox, successful exploitation can yield arbitrary code execution on the host. No public proof-of-concept was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 29, 2026
Remote code execution outside the browser sandbox can potentially be achieved by an unauthenticated attacker in Google Chrome versions prior to 154.0.8037.92 by exploiting a use-after-free in the Bluetooth subsystem. The victim must navigate to a crafted HTML page that exercises the Web Bluetooth code path (UI:R), and successful exploitation can lead to arbitrary code execution with a scope change (S:C), meaning a sandbox escape. No public exploit code or active exploitation has been identified at time of analysis, and a vendor patch is available in Chrome 154.0.8037.92.
RemediationAI
Vendor-released patch: update to Google Chrome 154.0.8037.92 or later immediately, as detailed in the Chrome release advisory (https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01807488085.html). For environments unable to patch immediately, consider disabling the Web Bluetooth API via enterprise policy (e.g., DefaultWebBluetoothGuardSetting set to 2 to block sites from requesting Bluetooth access) or by disabling the relevant feature flag, though this will break legitimate web applications that rely on Bluetooth connectivity. Additional compensating controls include enforcing site isolation and keeping the browser sandbox enabled; however, these do not fully mitigate the vulnerability. Monitor the Chromium issue tracker (https://issues.chromium.org/issues/556926296) for further updates.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a use-after-free (CWE-416) in the Bluetooth implementation of Chromium, the open-source project underlying Google Chrome. The Web Bluetooth API allows web pages to interact with Bluetooth devices; a crafted HTML page can trigger a memory corruption condition where a Bluetooth-related object is freed but subsequently dereferenced. Because the assessed vector includes a scope change (S:C) and the description states code execution can occur outside the sandbox, the flaw likely resides in a component with elevated privileges or can be chained to break the browser's sandbox boundary. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all platforms running Chrome builds earlier than 154.0.8037.92. Chromium issue 556926296 tracks the bug, and the severity is rated High by the Chromium team.
Know when Chrome gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-reachable via a crafted page (AV:N, AC:L, PR:N), requires the victim to open it (UI:R), and executes outside the sandbox (S:C) with full C/I/A impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Bluetooth in Google Chrome prior to 154.0.8037.92 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Articles & Coverage 1
Executive ViewAI
A critical use-after-free in Google Chrome's Bluetooth subsystem lets an attacker break out of the browser sandbox and execute arbitrary code on an affected endpoint, impacting any employee who browses the web with a Chrome version prior to 154.0.8037.92. Because the only prerequisite is that a user opens a crafted web page, exposure spans the entire workforce rather than a narrow technical group, and a sandbox escape means an endpoint compromise could escalate to broader network and data access. Google has shipped a fix, so the primary leadership decision is how quickly the organization can force a coordinated browser update.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13
Exploit-DB