Quick answers
- Is CVE-2025-48543 exploited in the wild?
- Yes. CVE-2025-48543 is known to be exploited in the wild, first recorded on 4 September 2025. Treat it as urgent.
- How severe is CVE-2025-48543?
- Critical severity, with a CVSS score of 8.8, published 4 September 2025.
- Which products and versions are affected?
- Google Android 13.0, 14.0, 15.0, 16.0.
- Is there a fix for CVE-2025-48543?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-48543 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2025-48543?
- Check whether you run Android Runtime or Google Android at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A use-after-free (UAF) vulnerability exists within the Android Runtime (ART) across multiple locations. An attacker can leverage this flaw to escape the Chrome browser sandbox and target the 'system_server' process. The exploit requires no user interaction and no additional execution privileges, resulting in a local escalation of privilege (EoP). This vulnerability is tracked as CVE-2025-48543 and has been added to the CISA Known Exploited Vulnerabilities (KEV) catalog. Google has released patches via the September 2025 Android Security Bulletin.
Affected products
- Google Android 13.0, 14.0, 15.0, 16.0
Timeline
- 2025-09-01: advisory: Vendor advisory published by Google in Android Security Bulletin
- 2025-09-04: disclosed: CVE published to NVD
- 2025-09-04: kev added: CISA added the vulnerability to the Known Exploited Vulnerabilities catalog