Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Android System local information disclosure due to missing permission check

IdentifiersCVE-2025-48604CWE-862· Missing Authorization

CVE-2025-48604 is an Android System information-disclosure vulnerability. According to the provided description, multiple code locations lack a required permission check, creating a path for one user to read files belonging to another user. This is a local flaw that does not require additional execution privileges and does not require user interaction. The core weakness is improper authorization enforcement around file access, resulting in cross-user data exposure within the Android System component.

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 allow a local attacker or malicious application to disclose files or file contents belonging to a different user on the same device. This breaks Android’s user isolation model and can expose sensitive user data without requiring privilege escalation or user interaction.

Mitigation

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

Until patches are applied, reduce exposure by limiting installation of untrusted local applications, enforcing application allowlisting where possible, and accelerating deployment of the December 2025 Android security update or vendor-equivalent firmware. Because exploitation is local and requires no user interaction, mitigation short of patching is limited.

Remediation

Patch, then assume compromise.

Apply the Android security updates that include the fix for CVE-2025-48604. The provided bulletin context indicates that Google’s December 2025 Android Security Bulletin addresses this issue, and devices updated to the 2025-12-05 patch level are described as fully remediated for issues disclosed in that bulletin.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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.

ACTIVITY FEED

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

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 malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

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 activity2

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