Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
HighCISA KEVExploited in the wildPublic exploit

Use-after-free privilege escalation in Android Runtime (ART)

IdentifiersCVE-2025-48543CWE-416· Use After Free

CVE-2025-48543 is a use-after-free vulnerability in the Android Runtime (ART) component. The issue is described as a memory-lifecycle flaw in ART that can leave a dangling reference after an object is freed, enabling attacker-controlled reuse of freed memory. Supporting content indicates the bug has been used as a Chrome sandbox escape on Android, with exploitation reachable from a compromised Chrome renderer and resulting in code execution in the privileged system_server process. The vulnerability affects Android 13 through 16 and was addressed in the September 2025 Android Security Bulletin / associated Google Play system updates. Google reported indications of limited, targeted in-the-wild exploitation.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can lead to local escalation of privilege from a less-privileged context into the highly privileged Android system_server context. In practical terms, this can enable full device compromise, including bypass of Chrome sandbox isolation, execution with elevated privileges, disabling of security controls, access to sensitive device data, and installation of persistent malware. The content also states exploitation has been observed in targeted real-world attacks and chained with Chrome renderer compromise for full device takeover.

Mitigation

If you can’t patch tonight, do this now.

Until patches are fully deployed, reduce exposure by prioritizing updates on devices running Android 13–16, especially those exposed to high-risk browsing or targeted attack scenarios. Because observed exploitation involved chaining from a compromised Chrome renderer, minimize risk by keeping Chrome and Android fully updated, restricting installation of untrusted applications, and relying on Google Play Protect / platform mitigations where available. Mitigation is limited because the vulnerability requires no user interaction once the attacker has the necessary local execution foothold.

Remediation

Patch, then assume compromise.

Apply the September 2025 Android security updates that address CVE-2025-48543. Devices should be updated to the September 2025 patch level (2025-09-01 or later; content also references 2025-09-05 for full bulletin coverage depending on device/vendor packaging) and receive the ART fix distributed through Google Play system updates where applicable. Ensure OEM/carrier updates are installed promptly on affected Android 13, 14, 15, and 16 devices.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2025-48543MaturityPoCVerified exploit

This repository contains a proof-of-concept (POC) exploit for CVE-2025-48543, a critical use-after-free vulnerability in the Android Runtime (ART) component affecting Android versions 13 through 16. The repository consists of a single C++ source file (CVE202548543.cpp) implementing the exploit logic and a detailed README.md explaining the vulnerability, exploitation steps, and real-world considerations. The exploit works by creating and freeing large Java String objects via JNI to trigger a use-after-free condition in ART, then performing heap spraying to overwrite freed memory with controlled data. It leverages the Android Binder IPC mechanism to communicate with and inject code into the highly privileged system_server process. The included shellcode is a placeholder for arbitrary code execution in the system_server context, demonstrating the potential for full device compromise and privilege escalation. The exploit is local in nature, requiring execution on a vulnerable Android device (pre-September 2025 patch). The code is structured as a JNI native library, with the main entry point being the trigger_use_after_free function, registered via JNI_OnLoad. The endpoints identified include the targeted Java class (java/lang/String), the JNI registration class (com/example/CVE202548543Exploit), and the system_server process. The README provides comprehensive documentation, including affected versions, impact, mitigation, and technical details of the exploit steps.

gamesarchiveDisclosed Sep 14, 2025c++local
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity36

Community discussion across Reddit, Mastodon, and other social sources.