External risk intelligence

Chromium Chromoting Use After Free Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-130929

This vulnerability exists within Chromoting, a client-side component of the Google Chrome browser used for remote desktop connectivity. It is a client-side feature typically used in controlled, end-user environments rather than acting as a public-facing network service or internet-exposed gateway.

Use After Free

Google Chrome

before 158.0.8127.36

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the Chromoting feature of Google Chrome, which could allow a remote attacker to execute arbitrary code. While the direct business impact is currently assessed as very unlikely due to the specific nature of the affected feature, it's important to confirm its relevance within your environment.

  • Code execution flaw in remote desktop feature.
  • It's a remote code execution vulnerability.
  • Confirm relevance and exposure; impact is low.

Attack Path

How an attacker could exploit the issue

A remote attacker could send specially crafted network traffic to a vulnerable system to trigger a use-after-free flaw in the Chromoting component. This could allow the attacker to execute code beyond the browser's sandbox.

  • Requires network access.
  • Triggered by crafted network traffic.
  • Arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chromoting, when supported, could allow a remote attacker to execute arbitrary code outside the sandbox by sending specially crafted network traffic. This could impact the integrity and confidentiality of the affected system.

  • Arbitrary code execution outside the sandbox.
  • Exploited via crafted network traffic.
  • System compromise and data loss.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Chromoting, a Google Chrome feature for remote desktop connectivity, likely impacts end-user devices managed by endpoint or desktop support teams. The immediate practical first step is to identify all instances of the affected Chrome version, assess their network exposure, and determine if they are business-critical or accessible by unauthenticated remote users. Once identified, the owner should be confirmed, and a risk-based remediation plan, potentially involving vendor coordination or temporary mitigation, should be developed.

  • Confirm Chromoting ownership and exposure.
  • Verify network reachability and business criticality.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Chromoting in Google Chrome?

Chromoting is a client-side feature built into the Google Chrome browser that enables remote desktop connectivity. It allows users to access computers or applications from a distance. Because it is designed for end-user interaction rather than acting as a public-facing network gateway, it is typically found on individual workstations and managed devices rather than on infrastructure servers.

What does CVE-2026-130929 mean by use-after-free?

This vulnerability is classified as CWE-416, or 'Use After Free.' It happens when a program continues to use a memory address after that memory has been cleared or deleted. By sending specifically crafted network traffic to the Chromoting component, an attacker can manipulate this memory error to trick the system into executing unauthorized code outside of the browser's normal security boundaries, known as the sandbox.

How is this vulnerability triggered?

An attacker must send crafted network traffic to the vulnerable Chromoting component to trigger the flaw. It is important to note that this is not triggered by standard, benign remote desktop usage. The vulnerability requires a specific sequence of network data to exploit the memory management error; simply having the Chromoting feature enabled on a system does not automatically make it susceptible to remote exploitation without this malicious input.

Is my organization at risk from this vulnerability?

According to Halo Surface Signal, this vulnerability is considered very unlikely to pose a high risk for most organizations. Because Chromoting is a client-side feature used in controlled, end-user environments, it rarely functions as an internet-exposed service. You should prioritize assets where this component is reachable by unauthenticated remote users or where it handles sensitive remote access sessions.

What should I do if I run Google Chrome?

Your first step is to locate systems in your environment that are running Chrome versions older than 158.0.8127.36. Once identified, evaluate whether these devices require remote access via Chromoting and verify their network reachability. Coordinate with desktop support teams to prioritize updates for any machines that are business-critical or have wider network accessibility, ensuring you maintain a standard patching cadence for all browser software.

References