In multiple locations, there is a possible way to escape chrome sandbox to attack android system_server due to a use after free.
Android 13, 14, 15 and 16 include the fix for this use-after-free, which can lead to local privilege escalation via a Chrome sandbox escape into system_server. No vendor rating is given; CVSS is 8.8.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 13, 14, 15, 16
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The vulnerability affects Android and Chrome, allowing an attacker to break out of the Chrome sandbox and target the Android system_server process. Successful exploitation could lead to local escalation of privileges without requiring user interaction or additional execution privileges.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CVE published
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
Affected versions
- Google Android
16, 15, 14, 13
References 2
android.googlesource.com
source.android.com
Questions about CVE-2025-48543
What does this mean?
A use-after-free bug in several locations can let an attacker escape the Chrome sandbox and escalate privileges locally, reaching the Android system_server process. No additional execution privileges are needed.Source: source.android.com
Am I affected, and how do I check?
The checked facts do not list affected version ranges. Compare your Android version against the advisory's fixed versions, 13, 14, 15 and 16.Source: source.android.com
What should I do about it?
Install an Android security update for version 13, 14, 15 or 16 that includes this fix.Source: source.android.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-09-04, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data