Chromoting in Google Chrome before version 150.0.7871.47 does not properly validate untrusted input received over the network, creating an input validation weakness (CWE‑20). The description indicates that a successful exploitation could lead to heap corruption, but the report does not explicitly state whether this would result in code execution or service disruption. Based on the wording "potentially exploit", it is inferred that an attacker might aim to achieve arbitrary code execution or cause a denial of service, but these outcomes are not confirmed by the available data.

Google Chrome installations earlier than version 150.0.7871.47 on any supported operating system are affected because the vulnerable Chromoting component is bundled with those releases.

The CVSS score of 8.8 indicates high severity, while the EPSS score of less than 1% indicates a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog, so no known active exploitation campaigns exist. An attacker would need to send crafted network traffic to the Chromoting service; no publicly documented exploit appears to exist yet, so the threat remains largely theoretical.