The vulnerability arises from an inappropriate implementation in Chrome’s navigation handling, classified as a CWE‑693 weakness that lacks adequate security controls. It allows a remote attacker who has already compromised a renderer process to deliver a specially crafted HTML page that triggers a sandbox escape, elevating the attacker’s privileges above those of the renderer. If the renderer remains compromised, the attacker can potentially achieve full system control with operating‑system level capabilities.

Google Chrome installations running any version earlier than 150.0.7871.47 are affected. Users who have not updated to this release are at risk.

The EPSS score of less than 1% indicates a low but nonzero probability of exploitation, while the CVSS score of 9.6 signifies a high severity. The issue is not listed in CISA’s KEV catalog, implying no known active exploits in the wild. Based on the description, it is inferred that the attacker would need to inject a crafted HTML document into the compromised renderer—potentially via malicious extensions, phishing, or other existing renderer‑compromise methods—to trigger the navigation bug. The exact initial vector is not specified, so the hypothesis of an extension‑based vector is marked as inference.