Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious low-privilege app
-
ExploitInvoke flawed SaveUi.java code path
-
ExecutionBypass package installation requirement check
-
ImpactEscalate to elevated local privileges
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 the attacker to already have local code execution on the device, typically via an installed application; the flaw lies in multiple functions of SaveUi.java where a logic error allows bypassing package-installation requirements. Per the CVSS vector no user interaction is needed (UI:N) and no additional execution privileges are required (PR:N / 'no additional execution privileges needed'). The principal limiting factor is the local attack vector (AV:L): this is not remotely reachable and presumes a malicious app already present on an affected build (Android 14, 15, 16, 16-qpr2, or 17); the exact feature-level trigger within SaveUi.java is not described in the available sources. |
| Impact | This is a legitimately high-severity local privilege-escalation issue (CVSS 8.4) but the signals converge on a 'patch-this-week, not emergency' posture rather than a drop-everything fire. The CVSS vector (AV:L/AC:L/PR:N/UI:N) describes a local, low-complexity flaw requiring no user interaction and, per the vector's PR:N, no additional privileges - consistent with the description that a malicious local app can bypass package-installation requirements with 'no additional execution privileges needed.' Note the internal tension worth flagging: PR:N normally denotes an unauthenticated attacker, yet this is a LOCAL vector (AV:L), so in practice it presumes an attacker who already has code running on the device (e.g., an installed app) but holds no special permissions - treat 'unauthenticated' here as 'no privileged app context required,' not 'remote.' The SSVC framework reports Exploitation: none and Automatable: no, with Technical Impact: total - i.e., full compromise if triggered, but no evidence of exploitation and not mass-automatable (it needs local presence). There is no CISA KEV listing, no EPSS score supplied, and no public exploit or PoC reference in the input. The vuln.today Decision label is 'this_week,' which aligns with high impact + absence of active exploitation. Bottom line: a real priority to patch on the normal monthly-bulletin cadence, not a zero-day emergency. |
| Exploit ScenarioDerived | A user installs a malicious or trojanized app that holds no special permissions. Leveraging the logic error in SaveUi.java, the app bypasses package-installation requirements to install or elevate components it should not be allowed to, achieving local privilege escalation without any user interaction. No public exploit code is identified in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 02, 2026
A logic error in multiple functions of SaveUi.java on Android 14, 15, 16, 16-qpr2 and 17 lets a locally installed application bypass package-installation requirements, yielding local escalation of privilege with high confidentiality, integrity and availability impact (CVSS 8.4, AV:L/PR:N/UI:N). The principal constraint is the local attack vector: the attacker must already have code running on the device, typically through an installed app, and the exact feature-level trigger inside SaveUi.java is not described in the available sources. No public exploit code and no active exploitation are indicated (SSVC Exploitation: none, Automatable: no), so this is a patch-this-week item rather than an emergency; the vendor bulletin is dated 2026-11-01.
RemediationAI
Apply the Android Security Bulletin of 2026-11-01 (https://source.android.com/docs/security/bulletin/2026/2026-11-01) and move devices to the patched build for their branch across Android 14, 15, 16, 16-qpr2 and 17; the bulletin is the authoritative source for the exact fix versions and patch levels, and no separate workaround is documented in the available sources. Until devices are updated, the practical exposure is limited to apps already installed on the device (AV:L, PR:N, UI:N), so restricting sideloading and third-party app sources and keeping the installed app inventory minimal reduce the attack surface, with the trade-off of reduced user flexibility for app installation.
Affected VersionsENISA
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
CWE-693 (Protection Mechanism Failure) in the Android SaveUi component: the Java code implementing the save/restore user-interface flow contains a logic error in multiple functions that causes the package-installation requirement check to be skipped or satisfied incorrectly, so a caller can complete an installation-related action that the platform should have blocked. Because the affected check is a protection mechanism rather than a memory-safety primitive, the impact is a straightforward permission/requirement bypass rather than memory corruption; CPE data pins the affected platform to google:android. The CVSS vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) confirms the flaw is only reachable from local context and requires neither user interaction nor additional execution privileges, but the sources do not describe which specific SaveUi.java functions are involved or what triggers the faulty logic.
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
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Local vector with an on-device app, no added privileges and no user interaction (AV:L/PR:N/UI:N); logic-error bypass yields total compromise, so C/I/A:H.
Primary rating from Vendor (google_android).
CVSS VectorVendor: google_android
Lifecycle Timeline
3DescriptionCVE.org
In multiple functions of SaveUi.java, there is a possible bypass of package installation requirements 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.
Articles & Coverage 1
Executive ViewAI
A high-severity logic flaw in Android's SaveUi component (CVE-2026-45514) allows a malicious app already installed on a device to bypass package-installation safeguards and gain elevated privileges, compromising data confidentiality, integrity, and availability. Leadership should be aware that this undermines Android's app isolation model, potentially enabling unauthorized access to sensitive corporate data on affected mobile devices.
No vendor patch identified at time of analysis. Interim mitigations: enforce application allowlisting and block sideloading via MDM/EMM; disable installation from unknown sources; use mobile threat defense to detect and block malicious apps; apply Google Play system updates where available; educate users on app-installation risks.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
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
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
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
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
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
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
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
EUVD-2026-115558
GHSA-ghqc-jxg9-p26j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB