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

CVE-2026-0078: In setGlobalProxy of DevicePolicyManagerService

In setGlobalProxy of DevicePolicyManagerService.java, there is a possible desync in persistence due to improper input validation. 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

A privilege escalation vulnerability exists in the setGlobalProxy function of Android's DevicePolicyManagerService. An attacker with a low-privilege local account can exploit improper input validation that causes a desync in persistence, requiring no user interaction and no elevated permissions beyond a basic account. Successful exploitation gives the attacker full read, write, and execution control over the affected device process. HarborGuard tracks this advisory and will make a patched-image rebuild available the moment Google publishes a fix.

HarborGuard Coverage

Detection

Detection is available across every HarborGuard environment; the CVE is ingested from upstream Android and Google security feeds within minutes of publication and matched against customer images, including custom-built Android-derived container images, in both registry scans and active pipeline checks.

Available
Triage

HarborGuard scores this CVE at 7.8 HIGH using the published CVSS v3.1 vector and weights it against each customer's per-environment compliance policy, then routes findings to the appropriate team inbox within the affected organization.

Available
Patch

Because no fix version has been published upstream, HarborGuard re-checks the advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment Google releases a corrected build. For customers with auto-remediation enabled, the rebuild, regression test run, and PR against affected workloads will be triggered without manual intervention as soon as the upstream patch lands.

Pending upstream

Exploit Conditions

  • Network reachabilityNot required

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

  • AuthenticationRequired

    Any low-privilege local account is sufficient; no admin or elevated credentials are needed beyond a basic user session.

  • Victim interactionNot required

    No user interaction is required; the attacker can execute the exploit entirely without involving another user.

  • Attack complexityDetail

    The exploit is reliable and condition-free; no race conditions, special memory layout, or specific environmental state is required.

Blast Radius

  • The attacker gains full read access to sensitive data held by the affected process, including credentials, session tokens, and device policy state.
  • The attacker can write or overwrite persisted configuration and policy data, altering device proxy settings and potentially broader system state.
  • The attacker achieves local privilege escalation, gaining execution capabilities beyond their original permission level on the device.
  • All three impact dimensions (confidentiality, integrity, availability) are rated High, meaning the attacker has complete control over the affected component.

How HarborGuard Handles This

Available on HarborGuard: detection for CVE-2026-0078 is active across all scanning environments for images derived from or shipping Android 14, 15, 16, or 16-qpr2. Because Google has not yet published a patched build, HarborGuard monitors the advisory on every ingest cycle and will surface a patched-image rebuild opportunity the instant a fix version is released upstream. For customers with auto-remediation enabled, the rebuild, regression test run, and PR against affected workloads will be triggered automatically at that point. In the interim, compensating controls worth considering include restricting local shell access to affected devices via network policy or device enrollment controls, applying egress filtering to limit lateral movement if a device is compromised, and auditing which workloads run with DevicePolicyManagerService exposure in your container images. Where compliance policy permits, HarborGuard can flag images containing affected Android versions as non-compliant to enforce quarantine until the upstream patch is available.

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