Skip to main content
Vulnerability Database/CVE-2026-106195

CVE-2026-106195: Google Chrome Chromoting Auth Bypass Flaw

CVE-2026-106195 is an authorization bypass flaw in Google Chrome Chromoting on Mac that allows attackers to circumvent system access restrictions through crafted network traffic. This article covers technical details, affected versions, security impact, and recommended mitigation strategies.

Published:

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-106195 Overview

CVE-2026-106195 is an incorrect authorization vulnerability in the Chromoting component of Google Chrome on macOS. Chromoting is the protocol stack that powers Chrome Remote Desktop. Versions of Chrome prior to 155.0.8059.39 fail to correctly enforce system access restrictions when processing certain network traffic. A remote attacker can send crafted packets to bypass those restrictions. Google rated the Chromium security severity as Low. The weakness maps to CWE-863: Incorrect Authorization.

Critical Impact

Remote attackers can bypass macOS system access restrictions enforced by Chromoting by sending crafted network traffic to a vulnerable Chrome install.

Affected Products

  • Google Chrome for macOS versions prior to 155.0.8059.39
  • Chromoting (Chrome Remote Desktop) component on macOS
  • Chromium-based builds that embed the vulnerable Chromoting code path

Discovery Timeline

  • 2026-10-06 - CVE-2026-106195 published to NVD
  • 2026-10-06 - Last updated in NVD database
  • Stable channel update - Google released the fix in Chrome 155.0.8059.39 for Desktop (Chrome Releases blog)

Technical Details for CVE-2026-106195

Vulnerability Analysis

The flaw sits in Chromoting, the remote desktop protocol stack shipped with Google Chrome. Chromoting handles session negotiation, authentication, and policy enforcement for Chrome Remote Desktop on macOS. The vulnerable code path performs an authorization check that does not fully validate the requester against the configured macOS system access restrictions. An attacker who can reach the Chromoting network endpoint can send crafted traffic that is accepted without the expected authorization gate. The result is access to functionality or resources that macOS policy should otherwise block. Google tracked the issue in Chromium Issue Tracker #553930843.

Root Cause

The root cause is incorrect authorization logic [CWE-863] inside the Chromoting component. The code grants access based on an incomplete or incorrectly scoped permission check. macOS enforces system-level restrictions on remote control, screen capture, and input injection. Chromoting is expected to honor those restrictions before servicing a remote request. The flawed check allowed specific crafted inputs to satisfy the control path without meeting the full policy requirement.

Attack Vector

Exploitation requires sending crafted network traffic to the Chromoting listener on a macOS host running a vulnerable Chrome build. The attacker does not need to execute code on the target first. Successful exploitation bypasses macOS access restrictions mediated by Chromoting. The published EPSS probability is 0.205% at percentile 9.558, indicating low near-term exploitation likelihood at disclosure. No public proof-of-concept, exploit, or CISA KEV listing is associated with this CVE at publication.

No verified exploit code is available. See the Chromium Issue Tracker entry and the Chrome stable channel update for vendor technical detail as it is unrestricted.

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 Attacks

Detection Methods for CVE-2026-106195

Indicators of Compromise

  • Chrome for macOS reporting a version earlier than 155.0.8059.39 in chrome://version or MDM inventory.
  • Unexpected Chrome Remote Desktop session establishment events on macOS endpoints not configured for remote access.
  • Inbound network connections to Chromoting-related ports on hosts where remote desktop was not authorized by policy.

Detection Strategies

  • Inventory all macOS endpoints and flag Chrome installs below 155.0.8059.39 as vulnerable.
  • Correlate process telemetry for remoting_host and related Chromoting binaries with network connection events to identify unauthorized session attempts.
  • Alert on Chrome Remote Desktop activation on devices where it is not sanctioned by configuration policy.

Monitoring Recommendations

  • Monitor macOS endpoints for Chromoting process launches outside expected business hours or from unmanaged devices.
  • Ingest Chrome update telemetry into the SIEM to confirm patch rollout coverage.
  • Track outbound signaling to Google remote desktop infrastructure from hosts not enrolled in remote access programs.

How to Mitigate CVE-2026-106195

Immediate Actions Required

  • Update Google Chrome on all macOS endpoints to 155.0.8059.39 or later through managed update channels.
  • Audit which macOS devices have Chrome Remote Desktop enabled and disable it where it is not required.
  • Validate that macOS Privacy and Security permissions for Screen Recording and Accessibility are scoped to approved applications only.

Patch Information

Google addressed CVE-2026-106195 in Chrome Stable 155.0.8059.39 for Desktop. Refer to the Chrome Releases announcement for the full change list and to Chromium Issue #553930843 for the underlying tracker entry. Chromium-derived browsers should pick up the fix once they rebase on the patched Chromium milestone.

Workarounds

  • Uninstall or disable the Chrome Remote Desktop host component on macOS endpoints that do not require remote access.
  • Enforce enterprise policy to block the Chromoting host from running via application allowlisting on macOS.
  • Restrict inbound network reachability to Chromoting listeners using host firewall rules until the patch is deployed.
bash
# Verify installed Chrome version on macOS and confirm it is at or above the fixed build
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version

# Disable the Chrome Remote Desktop host service on macOS (requires admin)
sudo launchctl unload /Library/LaunchAgents/org.chromium.chromoting.plist 2>/dev/null
sudo rm -f /Library/LaunchAgents/org.chromium.chromoting.plist

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.