Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall or run malicious local app
-
ExploitRegister unauthorized/excessive shortcuts
-
ExecutionExhaust ShortcutInfo resources
-
ImpactCrash launcher (local DoS)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires local access: the attacker must already be able to execute code on the device (e.g., a malicious or compromised installed application) that can create unauthorized shortcuts handled by ShortcutInfo.java. Given AV:L/AC:L/PR:N/UI:N, once local code execution exists no further privileges, no authentication, and no user interaction are needed, and default configurations are affected. The limiting factors are substantial: there is no remote attack surface (AV:L), the only impact is availability (a launcher crash - local denial of service with no confidentiality or integrity effect), and the attacker must first achieve app installation or local execution on the targeted device. |
| Impact | This is a genuine but low-urgency issue - a high-CVSS-feel that resolves to moderate real-world risk. The CVSS 3.1 score of 6.2 (MEDIUM) is driven entirely by availability impact (A:H) with no confidentiality or integrity loss (C:N/I:N), and the attack vector is explicitly local (AV:L), meaning an attacker must already be able to run code or install an app on the device. Although PR:N/UI:N indicate no privileges and no user interaction are required at the point of exploitation, the local vector means the practical precondition is a malicious or compromised app already present on the device. The signals align consistently rather than conflict: EPSS is very low (0.11%, 1st percentile), there is no CISA KEV listing, and no public exploit or PoC reference is provided - all consistent with a low-probability, low-consequence (crash-only) defect. The vuln.today decision label is 'this_month', not act_now or emergency, matching the SSVC-style read that technical impact is partial (availability only) and this is not automatable remote exploitation. Bottom line: a legitimate bug to patch on the normal monthly Android cadence, not a drop-everything priority; the worst outcome is a launcher crash (local DoS), not code execution or data exposure. |
| Exploit ScenarioDerived | A malicious or low-privilege app installed on an Android device registers or pushes an excessive/unauthorized set of shortcuts, exhausting resources in ShortcutInfo handling and crashing the system launcher, producing a local denial of service. No user interaction is required and no additional execution privileges are needed, but the attacker must already have local code execution (e.g., an installed app). No public PoC or exploit code is referenced. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
Local denial of service in Google Android 14, 15, 16, 16-qpr2 and 17 allows an already-installed application to crash the system launcher by publishing unauthorized shortcuts that exhaust launcher resources. The CVSS vector (AV:L/AC:L/PR:N/UI:N) means no additional privileges and no user interaction are needed once the attacker can execute code locally on the device, but the only consequence is an availability impact to the launcher - no confidentiality or integrity effect and no remote attack surface. Exploitation potential is constrained by that local-access prerequisite, EPSS is very low (0.11%, first percentile), and no public exploit has been identified at time of analysis.
RemediationAI
Apply the fix delivered through the Android Security Bulletin of 2026-11-01 (https://source.android.com/docs/security/bulletin/2026/2026-11-01), which is the vendor-published remediation path for this issue; the input data does not provide exact patched build or version identifiers, so device owners should adopt the bulletin's patch level for their branch (Android 14, 15, 16, 16-qpr2 or 17) via the OEM update channel - patch available per vendor advisory, and no exact fix version is stated. Because exploitation requires that the attacker already be able to run code locally on the device, typically through an installed application, exposure can be reduced at the deployment level by restricting installations to trusted or managed distribution channels (for example managed Google Play with sideloading disabled on managed fleets); the trade-off is reduced flexibility for users and developers who depend on sideloaded or enterprise-distributed APKs. No further vendor-specified workaround is given in the available references.
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
The flaw is classified as CWE-400 (Uncontrolled Resource Consumption) and resides in ShortcutInfo.java, part of the Android framework's shortcut plumbing that backs the ShortcutManager/launcher-shortcut APIs. ShortcutInfo objects describe dynamic and static shortcuts that an app publishes and that the launcher then binds, stores and renders; when an application supplies shortcut data that the launcher does not expect or authorize, the resulting resource exhaustion can take the launcher process down. The CPE cpe:2.3:a:google:android:*:*:*:*:*:*:*:* confirms the affected component is the Android platform itself rather than a standalone app, and EUVD enumerates Android 14, 15, 16, 16-qpr2 and 17 as affected versions. The CVSS metrics describe severity, not mechanism: the vector AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H states that the attack requires local execution context, that no privileges or user interaction are additionally required, and that the sole impact is high availability loss; the specific code path and trigger conditions are not described in the available sources beyond the ShortcutInfo handling of unauthorized shortcuts.
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:N/I:N/A:H
Local vector (malicious app) with no privileges or interaction and an easily triggered resource-exhaustion crash; impact is availability-only (launcher DoS), so C:N/I:N/A:H.
Primary rating from Vendor (google_android).
CVSS VectorVendor: google_android
Lifecycle Timeline
3DescriptionCVE.org
In ShortcutInfo of ShortcutInfo.java, there is a possible way to crash the launcher via unauthorized shortcuts due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.
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
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
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-115562
GHSA-cg9x-623v-28h5
NVD
CVE.org
EPSS
Exploit-DB