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

Cross-user image leak in Android PrintManagerService

IdentifiersCVE-2025-48628CWE-441· Unintended Proxy or Intermediary…

CVE-2025-48628 is an Android Framework information-disclosure vulnerability in PrintManagerService.java, specifically in the validateIconUserBoundary logic. According to the provided content, the flaw is caused by a confused deputy condition that can result in a cross-user image leak. In practice, this means the service can be induced to access or expose image data across Android user boundaries in a way that violates intended isolation. The issue does not require user interaction for exploitation and is described as enabling local escalation of privilege in the sense that an unprivileged local actor can obtain access beyond normal app or user-boundary restrictions.

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 disclose image data across Android user profiles or user boundaries, undermining Android's multi-user isolation model. The provided content characterizes the issue as a local escalation of privilege with no additional execution privileges needed, meaning a local attacker operating from a low-privilege context may gain access to data or capabilities not normally available to that context. The primary concrete impact described in the content is cross-user information exposure.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting installation and execution of untrusted local applications, especially on shared or multi-user Android devices where cross-user boundary violations have greater impact. Prefer fully managed device configurations, minimize use of multiple user profiles where operationally feasible, and accelerate deployment of OEM firmware updates aligned with the December 2025 Android bulletin. However, no complete mitigation is provided in the content aside from applying the vendor patch.

Remediation

Patch, then assume compromise.

Apply the Android security updates that include the fix for CVE-2025-48628. The provided content places this issue in Google's December 2025 Android Security Bulletin and indicates that devices updated to the 2025-12-05 patch level are fully remediated for issues disclosed in that bulletin. Enterprises should ensure OEM and vendor-provided updates incorporating the December 2025 Android fixes are deployed to affected supported devices.
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

5 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 activity4

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