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

Android System heap buffer overflow RCE in Media Codecs Mainline

IdentifiersCVE-2026-0006CWE-122· Heap-based Buffer Overflow

CVE-2026-0006 is a critical Android vulnerability in the System component, tied to the Media Codecs Mainline component on Android 16. The issue is described as occurring in multiple locations where a heap buffer overflow can cause out-of-bounds read and write conditions. The CVE record states that successful exploitation could lead to remote code execution. Available supporting content does not identify the exact vulnerable function or code path beyond the affected component context.

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 remote code execution in the affected Android System/Media Codecs context without requiring additional execution privileges and without user interaction. The published CVSS v3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) indicates high impact to confidentiality, integrity, and availability, consistent with full compromise of the vulnerable component and potential device-level impact depending on runtime context.

Mitigation

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

Primary mitigation is prompt patching via the March 2026 Android security update or applicable Google Play system update for Media Codecs Mainline. Where immediate patching is not available, risk reduction depends on standard Android platform mitigations and ensuring Google Play system updates are enabled and current on eligible devices. No specific workaround or feature-disable mitigation is provided in the supplied content.

Remediation

Patch, then assume compromise.

Apply the March 2026 Android security updates that address CVE-2026-0006. Devices at security patch level 2026-03-05 or later address all issues in the bulletin, and the bulletin also indicates a fix for CVE-2026-0006 is available through the Media Codecs Google Play system update/Mainline update path on eligible devices. OEMs and downstream integrators should incorporate the relevant AOSP and associated bulletin patches and ship them to supported devices.
PUBLIC EXPLOITS

Exploits

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

VALID 1 / 2 TOTALView more in app
CVE-2026-0006-openapv-pocMaturityPoCVerified exploit

This repository is a compact exploit/reproduction kit for CVE-2026-0006, a heap buffer overflow in libopenapv as integrated into Android 16's APV decoder path. It is not part of a larger exploit framework. The repository contains one delivery/generation path and two native proof-of-concept programs that validate the bug at the decoder level. Structure and purpose: - README.md documents the vulnerability, affected versions, setup steps, and expected crash behavior. - generate_overflow_mp4.py is the main exploit-building component. It reads a valid APV bitstream and a baseline MP4, prepends a forged AU_INFO PBU claiming 16x16 dimensions, preserves the original frame data that decodes as 64x64, patches MP4/APV metadata fields (apvC, apv1 sample entry, tkhd) to 16x16, replaces the mdat payload, and updates stsz/stco bookkeeping. The result is apv-mp4/overflow_auinfo.mp4. - deploy_exploit_mp4.sh operationalizes the exploit against a connected Android device/emulator: it generates the MP4, pushes it to /sdcard/Download/overflow_auinfo.mp4, triggers media scanning, opens it via Android VIEW intents (preferably in Google Photos), and inspects logcat for SIGSEGV/ASan-style crash evidence. - poc_mp4_asan.c is an end-to-end native PoC that mimics the Android C2SoftApvDec flow by parsing MP4 mdat content, checking the aPv1 signature, calling oapvd_info() to obtain attacker-controlled small dimensions, allocating buffers accordingly, and then calling oapvd_decode() where the larger real frame dimensions cause an out-of-bounds write. This is intended for ASan-instrumented confirmation. - poc_android_oob_write.c is a lower-level standalone PoC that loads an APV file directly, exercises oapvd_info()/oapvd_decode(), and includes a deliberate undersized-buffer test with guard bytes to measure overflow into adjacent memory. Main exploit capability: The exploit is a malicious media-file generator and deployment helper. Its core primitive is a dimension-confusion bug between metadata parsed by oapvd_info() and actual frame dimensions consumed by oapvd_decode(). This yields a heap out-of-bounds write during APV decoding. The repository demonstrates crash reproduction and the memory corruption condition that could underpin zero-click remote code execution when vulnerable Android media components automatically process the file for thumbnails/previews. Notable targeting details: The code and documentation specifically target Android 16 devices with APV codec support and pre-March 2026 patch levels, as well as upstream libopenapv versions v0.1.11.1 through v0.1.13.0. The Android delivery path relies on local adb interaction rather than remote network communication. No command shell payload or post-exploitation logic is included; the repository focuses on exploit file creation and vulnerability reproduction, making it operational but still primarily a crash/reproduction exploit rather than a full weaponized RCE chain.

mobilehackinglabDisclosed Apr 18, 2026markdownbashfileweblocal
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 activity19

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