Loading vulnerability…
CVE-2025-48626 is a privilege-escalation vulnerability in Android System affecting Android 13, 14, 15, and 16. The flaw is caused by a precondition check failure in multiple locations that can permit an application to be launched from the background when it should be blocked by Android’s protection logic. This weakness undermines intended execution and authorization constraints and can be used to bypass normal platform restrictions on background activity launches. The issue is described as requiring no additional execution privileges and no user interaction, and it has been characterized as enabling remote escalation of privilege.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical remote privilege escalation vulnerability in Google Android, caused by a precondition check failure that allows unauthorized application launch from the background. Exploitation does not require user interaction or additional privileges.
Android System component elevation-of-privilege vulnerability fixed in the December 2025 bulletin.
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.