Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconDevelop malicious app requesting benign permissions
-
DeliveryDistribute via third-party store or phishing
-
ExploitUser installs app on vulnerable Android device
-
InstallApp invokes handleUssdRequest exploiting logic error
-
C2Telephony permission check bypassed
-
ExecuteArbitrary USSD command dispatched to carrier
-
ImpactLocal privilege escalation to full device impact
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 a malicious app to be installed on the target Android device - the attacker must hold at minimum standard app-installation-level privileges on the device (CVSS PR:L, AV:L). Once installed, no additional permissions, elevated capabilities, special device configuration, or user interaction are needed to trigger the flaw; the vulnerable handleUssdRequest code path is reachable from a standard low-privilege app context on default Android configurations (CVSS AC:L, UI:N). The primary limiting factor is the local attack vector: the adversary must first achieve app delivery and installation, whether via social engineering, third-party app stores, phishing links, or physical access. No remote unauthenticated exploitation path exists. Exploitation is constrained to Android 14-17 (including 16-QPR2) devices running pre-September-2026 security patch levels. |
| Impact | The CVSS 7.8 High vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately captures a realistic local attack: a malicious app with only baseline installation-level privileges can reach the vulnerable code path with no user interaction and no elevated access. SSVC labels the technical impact 'total', consistent with the C:H/I:H/A:H triad, because unrestricted USSD dispatch can interact with carrier services in ways that affect confidentiality, integrity, and availability of both device and account. EPSS at 0.12% (2nd percentile) signals very low current exploitation probability, and no public exploit code or CISA KEV listing exists at time of analysis - SSVC exploitation status is 'none'. The primary real-world constraint is the local attack vector: the adversary must first achieve app installation on the target device, which substantially narrows opportunistic exploitation; even a mid-sized municipal IT team in sopot managing a corporate Android fleet should treat this as a standard monthly-patch-cycle priority rather than requiring emergency out-of-band remediation, unless sideloading controls are absent or the threat model includes targeted spyware delivery. |
| Exploit ScenarioDerived | An attacker publishes a malicious Android app requesting only innocuous-looking permissions (e.g., internet access, storage) and distributes it through third-party channels or phishing. Once installed with minimal privileges on a vulnerable device, the app directly invokes handleUssdRequest, exploiting the logic error to bypass the telephony permission gate and dispatch arbitrary USSD codes to the carrier - potentially triggering SIM-level operations, device resets, or further privilege escalation. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 10, 2026
Local privilege escalation in Android's telephony stack allows a low-privilege app to send USSD requests without the required telephony permission, bypassing Android's permission model through a logic error in handleUssdRequest of PhoneInterfaceManager.java. Affected releases span Android 14 through 17 including the 16-QPR2 branch, with no user interaction required post-installation. USSD access can reach carrier-side services capable of triggering sensitive device operations, making a successful exploit a pathway to full device compromise.
RemediationAI
Apply patches from the Android Security Bulletin for September 2026 (https://source.android.com/docs/security/bulletin/2026/2026-09-01) by updating devices to a security patch level of 2026-09-01 or later; exact OEM build numbers vary by manufacturer and must be verified via each OEM's release notes or device settings. The patch corrects the logic error in handleUssdRequest so the telephony permission check is properly enforced. For enterprise environments where OTA deployment is delayed, MDM administrators should enforce app installation restrictions to managed or approved sources only - this does not eliminate the vulnerability but reduces the delivery surface for a malicious app. Restricting unknown-source installs via Google Play Protect or enterprise policy and auditing installed app permissions for unnecessary telephony access are the most actionable interim compensating controls.
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
USSD (Unstructured Supplementary Service Data) is a GSM-layer signaling protocol that allows mobile handsets to communicate with carrier infrastructure - including code sequences that can initiate SIM operations, balance inquiries, and in some carrier configurations, destructive or reconfiguration commands. On Android, access to this interface is governed by the telephony permission framework enforced in PhoneInterfaceManager.java, part of the AOSP telephony service (com.android.phone). The vulnerability class is CWE-693 (Protection Mechanism Failure): the permission guard is architecturally present but a logic error in the handleUssdRequest code path renders it ineffective, allowing the check to be circumvented without explicitly defeating it. The flaw spans Android 14, 15, 16, 16-QPR2, and 17 as confirmed by the ENISA EUVD entry EUVD-2026-73977 and the Android Security Bulletin.
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:L/UI:N/S:U/C:H/I:H/A:H
Local attack vector via installed app (AV:L), low privilege required for installation (PR:L); total C/I/A impact because unrestricted USSD access enables carrier-level device operations.
Primary rating from Vendor (android).
CVSS VectorVendor: android
Lifecycle Timeline
3DescriptionCVE.org
In handleUssdRequest of PhoneInterfaceManager.java, there is a possible way to send a USSD request without permission 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
Android handsets versions 14 through 17 face a privilege escalation vulnerability that enables malicious apps to access carrier services without authorization, creating risk of corporate data exposure, unauthorized account activities, and full device compromise. Organizations managing Android device fleets should implement immediate controls to restrict untrusted app installation.
No vendor-released patch identified at time of analysis. Interim mitigations include: enforce application installation from official Google Play Store only; implement MDM policies to block sideloading and unknown sources; deploy application allowlist/blocklist controls; educate users on risks of untrusted applications; monitor logs for suspicious USSD activity; implement network segmentation to limit device access to sensitive systems.
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-73977
GHSA-q584-w9q9-2fgr
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB