CVE-2026-11635: Chrome Bluetooth Use-After-Free Sandbox Escape (macOS)

Technical summary

CVE-2026-11635 is a use-after-free (CWE-416) bug in Chrome's Bluetooth implementation on macOS prior to version 149.0.7827.103. The vulnerability occurs when a memory object is freed but later accessed without proper validation. An attacker controlling the renderer process can trigger this condition via malicious HTML, leading to arbitrary code execution in the privileged context outside the sandbox. The attack requires user interaction (visiting a crafted page) and depends on overcoming address space layout randomization (ASLR), reflected in the CVSS AC:H (attack complexity: high) rating.

Business impact

Successful exploitation allows an attacker to fully compromise a macOS system running Chrome. While the vulnerability requires a prior renderer compromise, it effectively negates the security boundary that isolates web content from the operating system. For organizations relying on browser sandboxing as a defense layer, this represents a critical escalation path. Affected users could face data theft, malware installation, or lateral movement into corporate networks.

Affected systems

Google Chrome versions prior to 149.0.7827.103 running on macOS are vulnerable. The Bluetooth component is implicated, though the HTML-based trigger vector suggests the flaw may be reachable through normal web browsing if a user's renderer process has already been compromised. Windows and Linux Chrome versions are not affected by this particular vulnerability.

Exploitability

Exploitation requires two preconditions: (1) compromise of the Chrome renderer process (typically through a separate browser vulnerability, malicious website, or malware), and (2) user interaction to visit the attacker-controlled HTML page. The CVSS score reflects high impact but moderate attack complexity due to ASLR mitigation. This is not remotely exploitable in a single step from an unauthenticated network position. However, in scenarios where a renderer is already compromised, exploitation becomes highly likely. The vulnerability is not currently tracked in the CISA Known Exploited Vulnerabilities (KEV) catalog, suggesting limited public exploitation at the time of publication.

Remediation

Update Google Chrome to version 149.0.7827.103 or later. Verify the update through Settings > About Google Chrome, which auto-checks for updates. For managed deployments, push this update immediately via your organization's Chrome deployment tools (Jamf, Intune, or equivalent MDM solutions). Interim mitigations include disabling Bluetooth-related features if not required, though sandboxing bypass protection ultimately depends on patching.

Patch guidance

Install Chrome 149.0.7827.103 or any subsequent release. This update addresses the use-after-free condition. Verify patch application by checking chrome://version/ after restart. For enterprise deployments, use your MDM system to enforce mandatory updates and audit compliance across devices. No manual configuration changes are required; patching is the sole remediation path.

Detection guidance

Monitor Chrome crash logs and system logs for unusual Bluetooth-related process termination or escalation events on macOS. Detection is challenging because the vulnerability exploits memory corruption; signature-based detection of the HTML trigger is not practical without access to attacker infrastructure. Focus on behavioral detection: watch for Chrome spawning unexpected child processes with elevated privileges or attempts to access sensitive system areas. Endpoint detection and response (EDR) tools should flag renderer process escalations. Threat hunting should prioritize systems running unpatched Chrome versions in conjunction with suspicious web activity.

Why prioritize this

Despite a CVSS score of 8.3 (HIGH), this vulnerability merits urgent patching because: (1) it enables sandbox escape, the last line of defense for browser-based attacks; (2) macOS users in security-sensitive roles are frequent targets; (3) the attack chain, while requiring an initial renderer compromise, is plausible in targeted campaigns; (4) the attack complexity is moderate, not exceptional. Prioritize patching ahead of routine updates but acknowledge that pre-existing renderer compromise is a dependency that may lower relative risk in environments with strong web filtering and malware prevention.

Risk score, explained

The CVSS 3.1 score of 8.3 reflects: (1) HIGH impact across confidentiality, integrity, and availability due to code execution outside the sandbox; (2) NETWORK attack vector allowing delivery via web content; (3) HIGH attack complexity reflecting ASLR and the need to achieve a precise memory state; (4) NO privilege requirement (the attacker leverages already-compromised renderer context); (5) REQUIRED user interaction (visiting the HTML page); and (6) CHANGED scope (escaping the sandbox affects the host OS, not just the browser process). The score appropriately captures a dangerous privilege escalation but does not account for the prerequisite renderer compromise, which some organizations may mitigate through separate controls.

Frequently asked questions