Skip to main content

Android CVE-2026-0084

| EUVDEUVD-2026-74048 HIGH
Protection Mechanism Failure (CWE-693)
2026-09-08 security@android.com GHSA-34jc-p6hm-mj7f
7.8
CVSS 3.1 · Vendor: android
View

Attack ChainAIDerived

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

  1. Access
    Social-engineer user to install malicious app
  2. Delivery
    App executes with low privileges on Android 16
  3. Exploit
    Trigger logic error in HostEmulationManager.java
  4. Execution
    Launch unauthorized background activity
  5. Persist
    Gain elevated process context
  6. Impact
    Full device C:H/I:H/A:H compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
Exploitation Conditions

Exploitation requires that a malicious or compromised low-privilege application be installed and running on the target Android 16 or Android 16-QPR2 device; this is the initial foothold condition (PR:L per CVSS). The logic error is in HostEmulationManager.java, meaning the NFC Host Card Emulation subsystem must be present (standard on modern Android devices). No user interaction is required at exploitation time once the app is installed (UI:N). What limits exploitation: the attack is local (AV:L), requiring physical device access or a social-engineering vector to install the initial app; it does not apply to Android versions other than 16 and 16-QPR2; and SSVC Automatable: no indicates the exploit cannot be trivially scripted for mass targeting.

Impact

The CVSS 7.8 score (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects a meaningful local privilege escalation: an attacker needs only a low-privilege app installed on the device and no user interaction at exploit time, with full confidentiality, integrity, and availability impact. EPSS is very low at 0.12% (2nd percentile), consistent with SSVC Exploitation: none, indicating no observed in-the-wild abuse at time of analysis. The SSVC Technical Impact rating of 'total' aligns with the CVSS impact triad; however, Automatable: no limits scalable mass exploitation. Even a mid-sized municipal IT team in leszno managing a mixed Android 16 fleet should treat this as a priority patch given that insider threat or malware delivery scenarios require only a sideloaded or malicious Play Store app to achieve full device compromise. The primary limiting factor is physical or remote access to deploy the initial low-privilege app - once that precondition is met, exploitation requires no further interaction.

Exploit ScenarioDerived

A threat actor distributes a malicious Android app - via phishing, a rogue MDM profile, or a trojanized sideload - that appears benign and requests only minimal permissions. Once installed and running in the background, the app triggers the logic error in HostEmulationManager.java to launch a privileged background activity, hijacking the UI and gaining full device control without prompting the user for additional permissions or confirmation. No public proof-of-concept code has been identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.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 10, 2026

Local privilege escalation in Android 16 and 16-QPR2 allows a low-privileged app to escalate to full device control by exploiting a logic error in HostEmulationManager.java that permits unauthorized background activity launches. The flaw stems from CWE-693 (Protection Mechanism Failure) in the activity-launch gating logic, enabling an installed malicious app to bypass Android's background activity restrictions without requiring additional permissions or user interaction. No public exploit has been identified and CISA has not added this to KEV, but SSVC rates the technical impact as total given that successful exploitation yields C:H/I:H/A:H on the device.

RemediationAI

Apply the September 2026 Android Security Bulletin patches available at https://source.android.com/docs/security/bulletin/2026/2026-09-01. OEM device manufacturers will incorporate these patches into their own monthly security updates; users should update to a security patch level of 2026-09-01 or later. No specific exact patched build version beyond the bulletin date was independently confirmed in the available data. As a compensating control where patching is delayed, enterprise MDM administrators can restrict installation of untrusted applications via managed device policies, which eliminates the prerequisite low-privilege app delivery vector. Disabling NFC on devices where it is not operationally required removes exposure of the HostEmulationManager code path, though the trade-off is loss of contactless payment and card emulation functionality.

Affected VersionsENISA

Android 16
Android 16-qpr2

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

HostEmulationManager.java is a component within the Android NFC Host-based Card Emulation (HCE) subsystem, responsible for routing APDU commands between card-emulating apps and NFC readers. Android's background activity launch restrictions are a core protection mechanism preventing unprivileged apps from abruptly launching foreground activities or hijacking the UI. CWE-693 (Protection Mechanism Failure) describes failures where a product does not use or incorrectly uses a protection mechanism, which here manifests as a logic error across multiple functions in HostEmulationManager.java that allow a background activity launch to proceed when it should be blocked. Affected versions per EUVD-2026-74048 are Android 16 and Android 16-QPR2; CPE strings were not provided but the platform is identifiable from the security@android.com reporter and the Android Security Bulletin reference.

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 (android) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local attack requiring only a low-privilege installed app; no user interaction; full device impact with no scope change beyond the compromised system.

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 (android).

CVSS VectorVendor: android

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

Lifecycle Timeline

3
CVSS changed
Sep 10, 2026 - 16:22 NVD
7.8 (HIGH)
CVE Published
Sep 08, 2026 - 19:17 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 08, 2026 - 19:17 cve.org
HIGH 7.8

DescriptionCVE.org

In multiple functions of HostEmulationManager.java, there is a possible background activity launch due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Executive ViewAI

Why It Matters

Android 16 and 16-QPR2 users face a local privilege escalation risk where installed malicious apps can achieve complete device control without requiring additional permissions or user interaction. Organizations managing Android device fleets should prioritize identifying affected devices and implementing protective measures, as no vendor patch is currently available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Implement Mobile Device Management application allowlisting to prevent unauthorized app installation; restrict device app sources to Google Play with enhanced security scanning; implement app permission policies restricting background activity; disable device sideloading and alternative app stores; audit and remove unnecessary applications; enable enhanced monitoring of background process behavior through endpoint detection tools.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
High
Android 16 is Google's latest major Android release, widely deployed on flagship devices
Data Quality
5 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 HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
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