Google Chrome’s Chromoting implementation contains a use‑after‑free bug that can be triggered by a crafted malicious file. When a local user opens the file, the freed memory can be reused to execute arbitrary code with the privileges of the current user. This flaw leads to a local privilege escalation, allowing an attacker to gain system level rights. The weakness aligns with CWE‑416, a memory management flaw.

Chromium users running Google Chrome on Windows with a version older than 148.0.7778.96 are vulnerable. The issue affects the stable channel and any custom builds that include the same Chromoting implementation.

The vulnerability is local; an attacker must have access to the target machine’s file system to deliver the malicious payload. EPSS data is unavailable, and the flaw is not listed in CISA’s KEV catalog. However, a CVSS score of 7.8 indicates high severity, suggesting that, if an attacker can supply a malicious file, they can raise their privileges quickly.