Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local execution on HarmonyOS 6.1.0 device
-
DeliveryInvoke unpermissioned key management API
-
ExploitTrigger permission control bypass
-
ExecutionCrash or exhaust key management subsystem
-
ImpactAvailability impact on device
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V8 - Authorization Permission and access control
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation 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 code execution on a HarmonyOS 6.1.0 device - specifically, the ability to invoke APIs in the device key management module from an unprivileged context. The CVSS PR:N metric indicates no prior privileges are required; any locally executing application or process can attempt exploitation. No network access, no user interaction, and no special system configuration are required beyond having local execution on the target device. Exploitation is limited to HarmonyOS 6.1.0 and is constrained by physical or logical access to the device (AV:L); remote attackers without a pre-existing foothold on the device cannot exploit this directly. SSVC confirms the attack is not automatable, suggesting reliable exploitation may require device-specific conditions or timing. |
| Impact | The CVSS 3.1 base score of 6.2 (Medium) reflects a local attack vector with no privilege requirement and high availability impact, but no confidentiality or integrity impact (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). This is an unusual combination: PR:N on a local vector means any process or app running on the device - without elevated rights - can trigger the flaw. SSVC signals corroborate a measured response: exploitation is currently 'none,' the attack is not automatable (SSVC: Automatable: no), and technical impact is only partial. There is no CISA KEV listing and no public exploit identified. EPSS data is not provided in the source intelligence, limiting probabilistic exploitation forecasting. The 'Privilege Escalation' tag in the source intelligence appears inconsistent with the CVSS impact metrics (C:N/I:N), suggesting the tag may reflect the nature of the vulnerable module rather than a confirmed privilege escalation outcome - defenders should verify with the vendor advisory whether escalation of privilege is achievable or if the impact is strictly a denial-of-service. Overall, this is a credible but currently low-exploitation-pressure finding, appropriate for standard patching cycles rather than emergency response. |
| Exploit ScenarioDerived | A malicious application installed on a HarmonyOS 6.1.0 device - without requiring any special permissions - invokes key management module APIs that should be restricted to privileged callers, triggering an unhandled state that crashes or hangs the subsystem and rendering the device or affected service unavailable. No public proof-of-concept code has been identified at time of analysis, and SSVC confirms exploitation is currently not observed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 17, 2026
Permission control failure in HarmonyOS 6.1.0's device key management module allows a local, unprivileged actor to cause a complete availability loss on the vulnerable system. The flaw is classified under CWE-264 (Permissions, Privileges, and Access Controls), indicating improper enforcement of access restrictions within the key management subsystem. SSVC assessment confirms no known exploitation and non-automatable attack, but the local-no-privilege vector lowers the bar for any co-located attacker or malicious app on the device.
RemediationAI
Consult the Huawei August 2026 security bulletin at https://consumer.huawei.com/en/support/bulletin/2026/8/ for the patched HarmonyOS build version; the exact fixed release version is not independently confirmed in available intelligence beyond vendor bulletin references. Users should apply the OTA update issued with that bulletin as the primary remediation. As a compensating control pending patch application, restricting installation of untrusted third-party applications reduces the local attack surface, since exploitation requires local code execution on the device. Disabling or sandboxing apps that interact with device key management APIs via HarmonyOS permission policies may further limit exposure, though this may affect device functionality relying on key attestation. No workaround fully substitutes for the vendor patch given the nature of the permission control gap.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in Huawei HarmonyOS 6.1.0 (CPE: cpe:2.3:a:huawei:harmonyos:*:*:*:*:*:*:*:*), specifically within the device key management module. CWE-264 (Permissions, Privileges, and Access Controls) identifies the root cause as an inadequate or missing permission check, meaning the module fails to correctly gate access to sensitive key management operations. HarmonyOS is Huawei's proprietary mobile and IoT operating system; its key management subsystem typically handles cryptographic material for device attestation and secure storage. A missing or bypassable permission control at this layer can allow untrusted local code to interact with functionality reserved for privileged or system-level callers.
Know when Harmonyos 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 confirmed by description; no privileges needed per CVSS source; pure availability impact with no confidentiality or integrity effect.
Primary rating from Vendor (huawei).
CVSS VectorVendor: huawei
DescriptionCVE.org
Permission control vulnerability in the device key management module. 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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Out-of-bounds heap write in Huawei HarmonyOS WEB module allows unauthenticated remote attackers to execute arbitrary cod
Permission 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)
The DP module has a service hijacking vulnerability.Successful exploitation of this vulnerability may affect some Super
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)
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
EUVD-2026-60071
GHSA-qqgg-59wm-3ggh
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB