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

Android Framework dumpBitmapsProto Missing Permission Check Local Privilege Escalation

IdentifiersCVE-2026-0047CWE-280· Improper Handling of Insufficient…

CVE-2026-0047 is a critical Android Framework elevation-of-privilege vulnerability affecting Android 16-QPR2. The flaw is in dumpBitmapsProto in ActivityManagerService.java, where a missing permission check allows an application to access private information it should not be able to read. According to the provided context, exploitation is local, requires no additional execution privileges, and does not require user interaction. The issue is documented as enabling local escalation of privilege, and some reporting notes it may be useful in exploit chains that culminate in broader code-execution outcomes.

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 allows a local application to bypass intended access controls and obtain private information from the vulnerable component. Because the flaw is classified as an elevation-of-privilege issue, it can let an attacker-app gain capabilities beyond its intended sandbox or permission set. The provided CVSS vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) indicates high potential impact to confidentiality, integrity, and availability. In practice, this makes the bug valuable as a post-compromise primitive for chaining with initial access or code-execution vulnerabilities.

Mitigation

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

Until patched builds are deployed, reduce exposure by restricting installation of untrusted or unnecessary local applications, enforcing application allowlisting where feasible, and using managed enterprise controls to limit sideloading and developer-oriented configurations. Because this is a local flaw with no user interaction required, mitigation primarily depends on preventing attacker-controlled code from running on the device and maintaining current OEM security updates. The provided context also notes that severity assumptions may consider platform and service mitigations disabled for development purposes or bypassed, so production hardening should remain enabled.

Remediation

Patch, then assume compromise.

Apply the Android March 2026 security updates that address CVE-2026-0047. The provided context states patches are available via the Android Open Source Project (AOSP) and that the issue is covered by the Android Security Bulletin dated 2026-03-01. Devices should be updated to an OEM-provided build incorporating the relevant March 2026 Android security patch level, with particular attention to Android 16-QPR2 deployments.
PUBLIC EXPLOITS

Exploits

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

VALID 1 / 1 TOTALView more in app
CVE-2026-0047-pocMaturityPoCVerified exploit

Repository is a standalone Android PoC for CVE-2026-0047, a missing permission check in ActivityManagerService.dumpBitmapsProto() on vulnerable Android 16 QPR2 Beta builds. It contains two Android application modules plus an automation script. The app/ module is an audit/demo PoC with a UI that can enumerate system services, test Binder dump exposure, simulate the vulnerable/patched behavior via a local FakeAmsService, and trigger the real Binder-based exploit path against the Android 'activity' service. The attacker/ module is a more realistic disguised app ('Flashlight Pro') that silently performs data harvesting and demonstrates exfiltration behavior, including scanning readable /proc files, installed packages, settings/content-provider accessible data, and external storage paths, then attempting the same bitmap-dump abuse. Both modules include local simulated vulnerable services to illustrate the bug class and patch. The main exploit capability is local privilege bypass/information disclosure via raw Binder IPC, not remote network exploitation. The shell script exploit.sh automates emulator setup, vulnerability probing with 'service call activity 117', APK build/install, UI interaction to trigger exploitation, and extraction of resulting bitmap artifacts from app-private storage. The exploit uses a crafted Parcel/ParcelFileDescriptor pipe to invoke dumpBitmapsProto() without android.permission.DUMP, then parses returned protobuf-like output for embedded PNG signatures and extracts stolen UI images. This is a real exploit PoC rather than just a detector, though it is operational/demo-grade rather than framework-weaponized. No hardcoded C2 or external exfiltration endpoints are present; exfiltration is local to device/app storage and host-side ADB retrieval.

mobilehackinglabDisclosed May 1, 2026javabashlocalfile
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 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 activity7

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