CVE-2025-48543 is a use-after-free vulnerability in the Android Runtime (ART) component affecting Android 13 through 16. The flaw arises from improper memory management and object lifetime handling in ART, leaving a dangling reference after an object has been freed. Available reporting indicates the issue is reachable in exploitation chains from a compromised Chrome renderer and has been used to escape the Chrome sandbox by triggering vulnerable ART behavior during Java object deserialization and parcel handling, resulting in execution within the highly privileged system_server process. The vulnerability requires no user interaction and no additional execution privileges, and has been observed in limited, targeted in-the-wild exploitation.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
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.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
54 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An Android vulnerability reported as exploited in targeted attacks; details not provided in the snippet.
A use-after-free vulnerability in Android Runtime, exploited as part of Predator spyware campaigns to gain initial access to Android devices.
A local privilege escalation vulnerability in Android Runtime that was actively exploited.
An unspecified vulnerability in Android Runtime.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.