Android Chrome Sandbox Escape via Use-After-Free
Actively exploited in the wild. Patch or mitigate immediately — don't wait for a maintenance window.
An attacker with a basic user account, with local access to the host, with no user interaction, can fully compromise the system — steal data, tamper with it and take it offline.
In multiple locations, there is a possible way to escape chrome sandbox to attack android system_server due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Inferred from the weakness type (CWE) and how the flaw is reached — the techniques an attacker would chain to exploit this. Real-world corroboration appears here as threat intel is folded in.
Corroborated threat activity referencing this CVE — with source and confidence, not inference.
Named threat actors and observed ATT&CK techniques appear here as intel feeds are folded in — the ATT&CK chain above stays inferred until then.
Generated by Wavense from the CVE record — an immediate mitigation and the permanent fix.
Implement advanced endpoint detection and response (EDR) solutions with behavioral analysis to detect anomalous activity originating from within the Chrome sandbox or related to system_server. Restrict unnecessary application installations and user permissions on Android devices to limit the attack surface. Monitor Android device logs for unexpected process creation, privilege changes, or unusual interactions involving the system_server process.
The permanent resolution requires applying the vendor-provided security update as soon as it becomes available. Monitor official Android security bulletins and Chrome release notes for the specific patch addressing this use-after-free vulnerability. Ensure all affected Android devices and Chrome installations are updated to the latest secure versions to remediate this critical privilege escalation.
An attacker can exploit this use-after-free vulnerability to escape the Chrome sandbox on an Android device. This leads to local escalation of privilege, allowing compromise of the critical system_server process without user interaction or additional execution privileges. Successful exploitation grants an attacker full control over the Android device, severely impacting data confidentiality, integrity, and availability.
Other CVEs affecting android
In Cellular Modem, there is a possible permission bypass due to a logic error in the code. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Out-of-bounds write in libimagecodec.quram.so prior to SMR Sep-2025 Release 1 allows remote attackers to execute arbitrary code.
Out-of-bounds write in libimagecodec.quram.so prior to SMR Apr-2025 Release 1 allows remote attackers to execute arbitrary code.
In multiple locations, there is a possible way to achieve code execution due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
In multiple locations, there is a possible way to launch activities from the background due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
there is a possible way to bypass due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
there is a possible way to bypass due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
In onCreate of WindowState.java, there is a possible way to launch a background activity due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.