HarborGuardharborguardDatabase
Back to search
HIGHCVE-2026-0100Published Modified CNA google_android

CVE-2026-0100: In Load of LoadedArsc

In Load of LoadedArsc.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Metrics

CVSS v3.1
7.8
Severity
HIGH
Fixed in
Affected Products
1

Get notified

Email me when this CVE is updated: new fix versions, severity changes, or any record change.

HarborGuard Analysis

Synopsis

This is a heap buffer overflow in Android's resource loading code, specifically in the Load function of LoadedArsc.cpp. An attacker with a low-privilege local account can trigger an out-of-bounds write without any user interaction, exploiting the flaw entirely from a shell or process already running on the device. Successful exploitation gives the attacker full read, write, and execution control over the affected process, enabling local privilege escalation. No fix version has been published yet; HarborGuard is tracking the advisory and will make a patched-image rebuild available the moment upstream ships a fix.

HarborGuard Coverage

Detection

Detection is available across every HarborGuard environment: the CVE is ingested from upstream Android security feeds and matched against customer images within minutes of publication, including custom-built images that bundle affected Android versions (14, 15, 16, 16-qpr2). Both registry scans and CI/CD pipeline checks are covered.

Available
Triage

HarborGuard scores this CVE at 7.8 HIGH using the published CVSS v3.1 vector and weights it against each customer environment's compliance policy to determine urgency and routing. Findings are sent to the inbox or ticket queue configured for the relevant team inside each customer org.

Available
Patch

No upstream fix is available for CVE-2026-0100 as of publication. HarborGuard re-checks the advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment Google publishes a corrected version; customers with auto-remediation enabled will receive the rebuild, a regression-test run, and a PR opened against affected workloads without manual intervention.

Pending upstream

Exploit Conditions

  • Network reachabilityNot required

    The attacker needs an existing shell or process on the host; no network access is required to reach the vulnerable code.

  • AuthenticationRequired

    Any low-privilege local account is sufficient; no elevated or administrative credentials are needed beyond basic shell access.

  • Victim interactionNot required

    No user action, click, or social-engineering step is needed; the exploit runs without any interaction from another user on the device.

  • Attack complexityDetail

    Attack complexity is low, meaning the exploit is reliable and requires no special race conditions, memory-layout guesswork, or environmental prerequisites.

Blast Radius

  • Reads any data accessible to the compromised process, including stored credentials, session tokens, and application files.
  • Overwrites memory and persisted data within the process's reach, enabling tampering with application state or stored records.
  • Escalates privileges beyond the initial low-privilege account, potentially gaining control over higher-privilege system processes or components.
  • Can destabilize or crash the affected service if the out-of-bounds write corrupts critical runtime structures.

How HarborGuard Handles This

Available on HarborGuard: this CVE is flagged immediately on any image found to include an affected Android version (14, 15, 16, or 16-qpr2), with triage routed according to each customer's configured compliance policy. Because no upstream patch exists yet, HarborGuard monitors the Google Android security advisory on every ingest cycle. In the interim, recommended compensating controls include restricting shell and adb access to the device, enforcing SELinux policy boundaries to limit what a low-privilege process can reach, and using network-policy isolation to reduce the attack surface of any services running on affected devices. The moment Google publishes a fix, a patched-image rebuild becomes available on HarborGuard; for customers who opt into auto-remediation, the rebuild, regression-test run, and PR against affected workloads are triggered automatically.

See how HarborGuard automates this
Affected packages
  • Google / Android
    16-qpr2 · 16 · 15 · 14
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H