A local attacker can bypass navigation restrictions in Google Chrome on Android by crafting a malicious file, allowing the attacker to navigate to disallowed locations or load content that should normally be blocked. The vulnerability originates from insufficient policy enforcement in DevTools and is classified as CWE‑20, indicating improper input validation or boundary checking. The flaw only enables local circumvention of navigation controls; it does not grant remote code execution or compromise other users' systems.

All installations of Google Chrome on Android running a build earlier than 150.0.7871.47 are vulnerable. Users on older Android devices using older Chrome versions are at risk.

The Chromium project rates the severity as Medium. No EPSS score or KEV listing is available, suggesting limited known exploitation. The exploit requires the attacker to deliver a malicious file to the device where the user can open or run it. Because the attack is local and tied to file access, threat exposure is confined to situations where the user can obtain or open such malicious content. The lack of remote exploitation vectors reduces the overall risk, but an active attacker with local access can still navigate beyond intended restrictions.