Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious app on device
-
DeliveryApp invokes restricted system call
-
ExploitPermission check logic fails to enforce access control
-
ExecutionRestricted resource accessed without authorization
-
ImpactLimited data disclosure, integrity modification, or availability disruption achieved
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Business logic errors
|
| Exploitation Conditions | Exploitation requires the attacker to have a locally executing process on the target device - most realistically, a malicious application installed on the HarmonyOS or EMUI device. The CVSS vector PR:N confirms no elevated OS privileges are required for the installed app to trigger the flaw; any sandboxed app can attempt the bypass. UI:N confirms no victim interaction (e.g., no tap or approval) is needed once the app is running. The primary limiting factor is the local attack vector (AV:L): the attacker cannot reach this vulnerability remotely over a network without first achieving app installation. Additionally, the low impact ratings (C:L/I:L/A:L) imply the permission bypass does not grant full device control - exploitation is bounded to whatever restricted resource the vulnerable call exposes. No specific configuration setting or non-default feature flag is identified in the description as a prerequisite; the flaw appears present in the default call-handling path. |
| Impact | The CVSS base score of 5.9 (Medium) reflects a constrained but real risk profile. The local attack vector (AV:L) significantly limits exploitability compared to network-exposed vulnerabilities - an attacker must have a foothold on the device, typically through a malicious application installed from an unofficial source or via prior compromise. However, PR:N and AC:L mean that once local access exists, exploitation requires neither elevated privileges nor complex setup, lowering the skill bar considerably. All three impact pillars (C:L/I:L/A:L) are assessed at low severity, consistent with a permission bypass that leaks limited data or disrupts specific functionality rather than achieving full system compromise. No EPSS score was provided in the input data - exploitation probability cannot be quantified. The absence from CISA KEV and lack of public POC suggest this is not currently being exploited in widespread campaigns. Overall, this is a medium-priority issue for HarmonyOS/EMUI deployments: not urgent for most enterprises, but relevant for high-assurance mobile environments where any unauthorized permission escalation by a sandboxed app is unacceptable. |
| Exploit ScenarioDerived | A threat actor distributes a malicious application - potentially disguised as a utility or game - that, once installed on the victim's HarmonyOS or EMUI device, invokes privileged system calls without holding the required permissions. Because the permission control logic contains a business logic gap, the call is serviced rather than rejected, allowing the app to read restricted data, modify limited system state, or degrade the availability of specific device functionality. No public exploit code has been identified at time of analysis, so exploitation currently requires independent rediscovery of the permission bypass. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 09, 2026
Permission control bypass in Huawei HarmonyOS and EMUI's call-handling subsystem allows a locally present, unprivileged attacker to circumvent intended access restrictions, resulting in low-level impacts to confidentiality, integrity, and availability. The vulnerability stems from improper business logic governing permission enforcement (CWE-840), meaning the system fails to correctly validate whether a calling entity holds the required permissions before servicing a request. No public exploit code exists and the vulnerability has not been listed in the CISA Known Exploited Vulnerabilities catalog, but the low attack complexity and absence of privilege requirements lower the bar for local abuse.
RemediationAI
The primary remediation is to apply the Huawei-issued patch referenced in the June 2026 Security Bulletin at https://consumer.huawei.com/en/support/bulletin/2026/6/. Users should update their HarmonyOS or EMUI devices to the patched build version specified in that bulletin - the exact fixed version is not independently confirmable from current input data and must be verified there. Since the attack vector is local and requires a malicious app to be present on the device, a meaningful compensating control in the absence of patching is to restrict application installation to the official Huawei AppGallery and disable sideloading (unknown sources). This limits the attacker's ability to deploy a weaponized app, though it does not address the underlying permission logic flaw. Enterprise MDM policies enforcing app allowlists on managed HarmonyOS/EMUI devices provide an additional layer of containment with the trade-off of reduced user flexibility.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
HarmonyOS and EMUI are Huawei's mobile/IoT operating system platforms. The affected component is the call-handling layer - likely inter-process communication (IPC), system API dispatch, or a similar call-routing mechanism - where permission checks are performed before servicing requests from applications or system components. CWE-840 (Business Logic Errors) indicates the flaw is not a classic memory-safety or injection issue but rather an incorrect or missing enforcement step in the permission validation flow: the logic controlling who is allowed to invoke certain calls contains a logical gap. The CVSS vector AV:L/AC:L/PR:N/UI:N confirms exploitation is strictly local (e.g., a malicious installed application), requires no special privileges, and needs no victim interaction. CPE strings cpe:2.3:a:huawei:harmonyos:*:*:*:*:*:*:*:* and cpe:2.3:a:huawei:emui:*:*:*:*:*:*:*:* cover all tracked versions of both platforms, with exact affected version ranges not narrowed in available CPE data.
Know when Emui 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:L/I:L/A:L
Primary rating from Vendor (huawei) · only source for this CVE.
CVSS VectorVendor: huawei
DescriptionCVE.org
Permission control vulnerability in calls. Impact: Successful exploitation of this vulnerability may affect availability.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in HarmonyOS Module Permission and Memory Flaws
View all 15Permission verification vulnerability in the wpa_supplicant module Impact: Successful exploitation of this vulnerability
Permission management vulnerability in the PMS module. Rated critical severity (CVSS 9.8), this vulnerability is remotel
Vulnerability of access permissions not being strictly verified in the APPWidget module.Successful exploitation of this
Vulnerability of permissions not being strictly verified in the window management module.Successful exploitation of this
API permission management vulnerability in the Fwk-Display module.Successful exploitation of this vulnerability may caus
Vulnerability of defects introduced in the design process in the HiviewTunner module. Rated critical severity (CVSS 9.8)
Vulnerability of out-of-bounds parameter read/write in the Wi-Fi module. Rated critical severity (CVSS 9.8), this vulner
Vulnerability of commands from the modem being intercepted in the atcmdserver module. Rated critical severity (CVSS 9.8)
Improper permission control vulnerability in the Notepad app.Successful exploitation of the vulnerability may lead to pr
Some smartphones have configuration issues. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitab
Some smartphones have the out-of-bounds write vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is r
Some smartphones have the out-of-bounds write vulnerability.Successful exploitation of this vulnerability may cause syst
EUVD-2026-35360
GHSA-595m-hf52-xp2j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB