Huawei HarmonyOS CVE-2025-58282
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall low-privilege app on device
-
ExploitInvoke camera module interface
-
ExecutionBypass permission control check
-
ImpactRead unauthorized confidential data
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 access to a HarmonyOS 5.0.1 or 5.1.0 device with at least low-level privileges already obtained - in practice, a malicious or compromised application running on the device that then abuses the camera module's permission-control flaw to reach camera data/services beyond its authorization. Limiting factors: the attacker cannot exploit this remotely or over a network (AV:L), must already hold some foothold/privilege on the device (PR:L), and gains only confidentiality disclosure with no integrity or availability impact (I:N/A:N) and no privilege scope expansion (S:U). The exact camera feature or configuration involved is not specified in the vendor description, so no non-default setting is known to be required. |
| Impact | This is a moderate-severity information-disclosure flaw (CVSS 5.5) in the HarmonyOS camera module, and the available signals consistently point to LOW real-world urgency rather than a top priority. The CVSS vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N shows exploitation requires LOCAL access (AV:L) and existing low privileges (PR:L) - i.e. an attacker must already be able to run code/an app on the device - and yields only confidentiality impact (C:H, I:N, A:N) with no scope change. EPSS is very low at 0.09% (0th percentile), the CVE is NOT on CISA KEV, and no public exploit code was identified, so all three exploitation signals agree: no evidence of active or imminent exploitation. There are no conflicting signals here - the local+low-privilege vector, negligible EPSS, and absence of KEV/POC align to indicate a bounded, locally-exploitable privacy issue most relevant in multi-app or malicious-app threat models rather than remote mass exploitation. The description is terse ('may affect service confidentiality') and provides no specific feature detail, which is the main data gap; vector-to-description consistency is reasonable (local permission-control flaw matches AV:L/PR:L). |
| Exploit ScenarioDerived | A malicious or low-privileged application already installed on a HarmonyOS 5.0.1 or 5.1.0 device abuses a permission-control weakness in the camera module to access camera-related data or services it should not be authorized to reach, disclosing confidential information to the attacker-controlled app. No user interaction is required (UI:N), but the attacker must already have local low-privilege execution on the device. No public proof-of-concept exploit was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Local information disclosure in Huawei HarmonyOS 5.0.1 and 5.1.0 allows an application that already holds low-level privileges on the device to reach camera data or camera-module services beyond its authorization, because the camera module's permission control is improperly enforced. Successful exploitation affects confidentiality only (CVSS 5.5, AV:L/AC:L/PR:L/UI:N, C:H/I:N/A:N) with no integrity or availability impact and no expansion of privilege scope. No public exploit code or confirmed active exploitation has been identified, and the EPSS score is 0.09% (0th percentile), so real-world urgency is low.
RemediationAI
Apply the HarmonyOS security update described in Huawei's October 2025 consumer bulletin (https://consumer.huawei.com/en/support/bulletin/2025/10/); patch availability per vendor advisory is indicated, but the exact fixed build or version number is not stated in the supplied data and should be confirmed against the bulletin or via Settings > System & updates on the device. Because there is no remote attack path, compensating controls focus on reducing the chance that a malicious or compromised app ever runs with local privileges: restrict installation to Huawei AppGallery or otherwise verified sources and avoid sideloaded APKs, which will block users who depend on third-party or enterprise-sideloaded software; audit and revoke camera permission for untrusted applications under Settings > Privacy > Permission manager > Camera, accepting that this disables legitimate camera use for those apps; remove or isolate untrusted apps inside a work profile, private space, or managed container so they cannot reach consumer-profile camera services, at the cost of added management overhead; and, in enterprise fleets, use MDM allow-listing of applications and HarmonyOS device-management policy to constrain which apps can run, which reduces flexibility for users who need unapproved tools. None of these controls substitute for the vendor update, and none mitigates an attacker who has already achieved code execution and legitimate low privileges on the device.
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 rooted in CWE-264 (Permissions, Privileges, and Access Controls), a deprecated category now best mapped to CWE-284 (Improper Access Control) and CWE-863 (Incorrect Authorization). HarmonyOS exposes camera functionality through system camera frameworks and services that applications normally reach only after the user grants the camera permission and after the module validates the caller's authorization. In this case the camera module's internal permission control is deficient, so a caller with low privileges (PR:L) can access camera-related resources it should not be able to read. The local attack vector (AV:L) and low attack complexity (AC:L) mean the adversary must already be executing code on the handset - typically a malicious or compromised app - and no user interaction is needed (UI:N) once that foothold exists. The scope is unchanged (S:U), so the bypass does not escalate the app into a higher-privilege context; it yields only confidentiality disclosure (C:H) with no write or denial-of-service capability. The exact camera feature, API, or configuration affected is not detailed in the vendor bulletin, and no non-default setting has been identified as a prerequisite.
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:L/UI:N/S:U/C:H/I:N/A:N
Camera permission-control bypass is reachable only by a local low-privileged app (AV:L/PR:L), needs no user interaction, and discloses confidential data only (C:H, I:N, A:N).
Primary rating from NVD.
CVSS VectorNVD
DescriptionNVD
Permission control vulnerability in the camera module. Successful exploitation of this vulnerability may affect service confidentiality.
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.
Affected Products (CPE)NVD
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
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB