Skip to main content

Google Android EUVDEUVD-2026-78995

| CVE-2026-57042 MEDIUM
Unintended Proxy or Intermediary ('Confused Deputy') (CWE-441)
2026-09-15 Google_Devices GHSA-rcx4-x4hm-jrrp
6.7
CVSS 3.1 · Vendor: Google_Devices
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Install malicious app on device
  2. Delivery
    Craft intent to DreamPickerReceiver
  3. Exploit
    Trigger confused-deputy permission bypass
  4. Execution
    Coerce System component to act
  5. Impact
    Escalate to System privileges

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service Proxy/intermediary controls
Exploitation Conditions

Requires the attacker to already have local code execution on the device - a malicious or compromised app installed and running - that can send intents to the DreamPickerReceiver component (the screensaver/Daydream picker). Exploitation is fully local (AV:L) with no user interaction (UI:N), so no phishing or click is required once the app is present. Limiting factors: no remote/network reach whatsoever, dependency on the confused-deputy permission-bypass path in DreamPickerReceiver.kt, and applicability to affected Android/Pixel builds per the September 2026 bulletin; devices patched with the 2026-09-01 security level are not exposed.

Impact

This is a genuine but locally-scoped Android privilege escalation. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 7.8 HIGH) is entirely local: an attacker needs code already running on the device (a malicious/low-privileged app) to abuse the confused-deputy flaw in DreamPickerReceiver.kt and reach System-level impact - there is no remote or network exposure. No EPSS score, no CISA KEV listing, and no public POC are present in the input, so this is not evidence of active or widespread exploitation; it reads as a routine monthly Android/Pixel-bulletin EoP hardening fix. NOTE A CONFLICT: the description states 'System execution privileges needed,' which would normally imply high privilege (PR:H) and a lower score, yet the assigned vector uses PR:L. The confused-deputy pattern (a low-privileged app tricking a System-privileged component) is consistent with PR:L, but the phrasing is ambiguous and should be verified against the Android/Pixel bulletin. Real-world priority is moderate: it is a valuable link in a local exploit chain (e.g., after a malicious app is installed) rather than a remotely weaponizable critical flaw.

Exploit ScenarioDerived

A user installs a malicious or trojanized app from a third-party source. The app sends crafted intents to the vulnerable DreamPickerReceiver, which - acting as a confused deputy - performs a privileged action on the attacker's behalf, bypassing a permission check and letting the app escalate to System execution privileges with no user interaction. No public exploit code was identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 16, 2026

Local privilege escalation in Google Android/Pixel arises from a permission bypass in the DreamPickerReceiver.kt component (the Daydream/screensaver picker), where a confused-deputy flaw lets a locally installed application reach privileged operations that execute with System privileges. Affected are Android/Pixel builds at security patch levels prior to the 2026-09-01 bulletin; exploitation requires the attacker to already have local code execution via a malicious or compromised app, and no user interaction is needed once that app is present. The issue is fully local (AV:L) with no remote or network reach, no public exploit code has been identified at time of analysis, and devices carrying the 2026-09-01 patch level are not exposed.

RemediationAI

Apply the vendor fix by updating affected Pixel/Android devices to the security patch level published in the September 2026 Pixel bulletin (2026-09-01), available via over-the-air system update; this is the only complete remediation and removes the confused-deputy path in DreamPickerReceiver.kt. Where immediate update is not possible, note that the exploit prerequisite is a locally executing malicious app, so the most effective compensating controls target app installation: enforce an MDM/enterprise app allowlist or rigorous Play Protect scanning and disable 'Install unknown apps' for all users (trade-off: blocks legitimate sideloading and some enterprise internal apps), and remove unnecessary or untrusted apps from high-value devices. Because the attack requires no user interaction, user-awareness training and phishing defenses provide no mitigation here, and there are no known network-side controls given the strictly local (AV:L) attack vector - the practical residual risk is limited to devices that cannot be patched, for which de-provisioning or isolating the device from sensitive data is the remaining option. Verify effectiveness by confirming the device security patch level shows 2026-09-01 or later, using the vendor advisory at https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01.

Affected VersionsENISA

Android Android kernel

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

DreamPickerReceiver is an Android broadcast/intent receiver that handles requests related to the Daydream screensaver picker. As a component that can be addressed by other apps on the device, it sits on the Android Binder/IPC trust boundary between untrusted application processes and privileged framework code running in system_server. CWE-441 (Unintended Proxy or Intermediary, i.e. a confused deputy) describes the root cause here: the receiver fails to sufficiently verify that the calling UID or package is authorized for the operation it performs, so a lower-privileged app can induce the higher-privileged receiver to act on its behalf and effectively inherit System-level execution context. The CVSS vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H reflects that a low-privileged local actor can achieve full compromise of confidentiality, integrity, and availability of the vulnerable component's security scope with no user interaction and no network vector. The CPE cpe:2.3:a:google:android:*:*:*:*:*:*:*:* indicates the flaw is tracked against the Android platform broadly, with the fix distributed through Google's Pixel/Android monthly bulletin rather than a standalone application release.

Know when Android gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Google_Devices) PRIMARY 6.7 MEDIUM
AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local malicious app abuses a System-privileged deputy (AV:L, PR:L, UI:N); escalation to System yields full C/I/A impact, no scope change (S:U).

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Google_Devices).

CVSS VectorVendor: Google_Devices

Attack Vector
Local
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Severity Changed
Sep 16, 2026 - 16:22 NVD
HIGH MEDIUM
CVSS changed
Sep 16, 2026 - 16:22 NVD
7.8 (HIGH) 6.7 (MEDIUM)
CVSS changed
Sep 16, 2026 - 14:22 NVD
7.8 (HIGH)
CVE Published
Sep 15, 2026 - 18:34 cve.org
HIGH 7.8
CVE Published
Sep 15, 2026 - 18:34 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In multiple functions of DreamPickerReceiver.kt, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

Executive ViewAI

Why It Matters

Google Android/Pixel devices with security patch levels prior to 2026-09-01 are affected by CVE-2026-57042, a high-severity local privilege escalation that could allow a malicious or compromised app to reach System-level privileges on the device. No vendor-released patch identified at time of analysis, and no public exploit identified at time of analysis, but the flaw still creates meaningful enterprise risk for organizations that permit untrusted or sideloaded apps on mobile endpoints. Leadership should prioritize device inventory, app-install restrictions, and readiness to apply the 2026-09-01 Android/Pixel security patch level to protect corporate data and device integrity.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include enforcing managed Google Play or allowlist-only app installation, blocking sideloading and unknown sources, disabling developer options, restricting local code execution through EMM/MDM policies, monitoring for suspicious or compromised apps, and applying the 2026-09-01 Android/Pixel security update as soon as it is available.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
High
Android platform is enormous, but this appears in a Pixel-specific bulletin
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2015-3105 CRITICAL POC
10.0 Jun 10

Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466

CVE-2015-3864 CRITICAL POC
10.0 Oct 01

Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A

CVE-2013-4710 CRITICAL POC
9.3 Mar 03

Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp

CVE-2015-1538 CRITICAL POC
10.0 Oct 01

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef

CVE-2024-21633 HIGH POC
7.8 Jan 03

Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK

CVE-2017-13156 HIGH POC
7.8 Dec 06

An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability

CVE-2016-2107 MEDIUM POC
5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-3106 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2015-3107 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2013-4787 CRITICAL POC
9.3 Jul 09

Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows

CVE-2014-7911 HIGH
7.2 Dec 15

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.

CVE-2016-0801 CRITICAL POC
9.8 Feb 07

The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy