The vulnerability is a classic use‑after‑free that occurs in Chrome’s USB handling code on macOS. When a renderer process that has already been compromised processes a specially crafted HTML page, it can dereference freed memory and inject code that breaks out of the sandbox. This classic buffer misuse aligns with CWE‑416 and can potentially expose the victim’s system to arbitrary code execution once the sandbox boundary is traversed.

Google Chrome on macOS versions that precede 150.0.7871.47. The issue is limited to the desktop stable channel and affects users running older releases; newer releases contain the fix.

The defect is rated as high severity by Chromium’s internal scoring. No EPSS value is available, but the lack of public exploits in KEV does not diminish the potential impact. Attackers only need to get a malicious HTML page rendered by a compromised renderer process; the sandbox escape can then allow the attacker to execute code with the same privileges as the Chrome process, which on macOS typically includes broad system access.