CVE-2026-106195

chromium-browser: Incorrect authorization in Chromoting

Published Oct 6, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
Incorrect authorization in Chromoting in Google Chrome on on Mac prior to 155.0.8059.39 allowed a remote attacker to bypass system access restrictions via crafted network traffic. (Chromium security severity: Low)

Analysis

AI-generated

Technical impact

An incorrect authorization check in the Chromoting component of Google Chrome on macOS allows a remote attacker to craft network traffic and bypass system access restrictions. The flaw is identified as CWE-863, meaning that an attacker can gain unauthorized access to a remote desktop session that could otherwise be protected by local system controls. This could enable the attacker to view or manipulate the user’s desktop environment, potentially exposing sensitive data or executing further actions on the host. The vulnerability is rated as critical with a CVSS score of 9.1, indicating a high overall risk to the system.

Affected Systems

Google Chrome on macOS versions prior to 155.0.8059.39 are affected. The vulnerability applies to any installation of Chrome where Chromoting is enabled and listening for incoming remote desktop connections.

Risk and Exploitability

Because the flaw is triggered by crafted traffic sent over the network, a threat actor must reach the target device and target the Chromoting service. The EPSS score is < 1% and the vulnerability is not listed in the CISA KEV catalog, indicating a low probability of exploitation in the wild. Nevertheless, the attacker can gain serious risk due to the high CVSS score of 9.1, which marks the vulnerability as critical. Updating to Chrome 155.0.8059.39 or later eliminates the flaw, while failure to patch leaves the system susceptible to unauthorized remote access via Chromoting.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Google Chrome on macOS to version 155.0.8059.39 or later
  • If an update is not currently feasible, disable Chromoting in Chrome’s settings or block inbound traffic to the Chromoting port so that no remote desktop traffic can reach the browser
  • Verify that network firewalls or local security policies block any external connections to Chrome’s Chromoting interface, preventing a remote attacker from reaching the vulnerable component

Generated by OpenCVE AI on October 8, 2026 at 14:34 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4833-1 chromium security update
Debian DSA Debian DSA DSA-6553-1 chromium security update
History
Type Values Removed Values Added
Title chromium-browser: Incorrect authorization in Chromoting
References
Metrics threat_severity

None

threat_severity

Low

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Chromoting Authorization Bypass in Google Chrome on macOS
Type Values Removed Values Added
First Time appeared Apple
Apple macos
CPEs cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
cpe:2.3:o:apple:macos:-:*:*:*:*:*:*:*
Vendors & Products Apple
Apple macos
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Type Values Removed Values Added
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome
Type Values Removed Values Added
Title Chromoting Authorization Bypass in Google Chrome on macOS
Type Values Removed Values Added
Description Incorrect authorization in Chromoting in Google Chrome on on Mac prior to 155.0.8059.39 allowed a remote attacker to bypass system access restrictions via crafted network traffic. (Chromium security severity: Low)
Weaknesses CWE-863
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
Oct 9, 2026, 9:47 PM
Reserved
Oct 6, 2026, 4:30 PM
Status
Modified
Published
Oct 6, 2026, 7:17 PM
Modified
Oct 9, 2026, 10:16 PM
Severity
Low
Public date
Oct 6, 2026, 6:41 PM