Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-106294 Overview
CVE-2026-106294 affects Google Chrome on macOS prior to version 155.0.8059.39. The flaw resides in Chromoting, the component that powers Chrome Remote Desktop. Incomplete cleanup of resources allows a remote attacker to bypass system access restrictions through crafted network traffic. Google rates the Chromium security severity as Low. The weakness maps to CWE-459: Incomplete Cleanup.
Critical Impact
A remote attacker can bypass system access restrictions on macOS hosts running vulnerable Chrome builds by delivering crafted network traffic to the Chromoting component.
Affected Products
- Google Chrome for macOS versions prior to 155.0.8059.39
- Chrome Remote Desktop (Chromoting) component on macOS
- Downstream Chromium-based browsers on macOS that embed the vulnerable Chromoting code
Discovery Timeline
- 2026-10-06 - CVE-2026-106294 published to the National Vulnerability Database
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-106294
Vulnerability Analysis
The vulnerability lives in Chromoting, the Chrome subsystem that implements Chrome Remote Desktop sessions. On macOS, Chromoting fails to fully release state or resources associated with a session or connection. An attacker who reaches the Chromoting network surface can abuse the leftover state to bypass system access restrictions enforced by the browser or the operating system. The issue is tracked publicly as Chromium Issue #556215048 and resolved in the Google Chrome Stable Update.
Root Cause
The root cause is incomplete cleanup [CWE-459]. When Chromoting tears down a session or releases a resource, it leaves artifacts behind that remain accessible or influence subsequent operations. Those residual artifacts allow access checks to be short-circuited.
Attack Vector
Exploitation requires a remote attacker to send crafted network traffic to a macOS host running a vulnerable Chrome build with Chromoting active. The attacker uses the residual state to bypass access restrictions that normally govern remote desktop or system interactions. No authenticated code execution on the target is required to begin the attack.
No verified proof-of-concept code is publicly available. See the vendor advisory for technical details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-106294
Indicators of Compromise
- Unexpected inbound connections to Chromoting listening ports on macOS endpoints.
- Chrome Remote Desktop session artifacts that persist after a session has been terminated.
- Chrome processes on macOS running versions earlier than 155.0.8059.39 while handling remote desktop traffic from unrecognized peers.
Detection Strategies
- Inventory installed Chrome builds on macOS fleets and flag any version string below 155.0.8059.39.
- Correlate Chrome Remote Desktop session logs with authentication events to identify sessions that bypass expected approval flows.
- Alert on Chromoting network traffic originating from untrusted source addresses or outside normal administrative hours.
Monitoring Recommendations
- Collect endpoint telemetry for the Chrome and remoting_host processes on macOS, including child process creation and network sockets.
- Monitor macOS TCC and system access prompts for Chrome to spot anomalous access grants following Chromoting activity.
- Ingest browser version telemetry into a central data lake to continuously verify patch state across the fleet.
How to Mitigate CVE-2026-106294
Immediate Actions Required
- Update Google Chrome on all macOS endpoints to version 155.0.8059.39 or later and restart the browser to apply the fix.
- Disable Chrome Remote Desktop on macOS systems that do not require it until the patch is confirmed deployed.
- Restrict inbound network access to Chromoting ports using host or network firewalls where remote desktop is not an operational requirement.
Patch Information
Google fixed the issue in the Chrome Stable channel release documented in the Stable Channel Update for Desktop. Upgrade macOS Chrome to 155.0.8059.39 or newer. The upstream Chromium fix is tracked in Chromium Issue #556215048.
Workarounds
- Uninstall or disable the Chrome Remote Desktop host component on macOS systems that do not need remote access.
- Enforce network segmentation so that only approved management subnets can reach Chromoting services.
- Require managed update policies through MDM to ensure Chrome auto-updates complete without user deferral.
# Verify installed Chrome version on macOS and confirm it is patched
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
# Expected output: Google Chrome 155.0.8059.39 or later
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

