VulnerabilityPublished 11 Oct 2025Updated 14 Oct 2025

CVE-2025-58282: Huawei HarmonyOS · Permissions, Privileges, and Access Controls

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 2.8 Low.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

2.8Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Huawei HarmonyOS	Affected =5.1.0 =5.0.1	Fixed in–

AI-suggested

To mitigate CVE-2025-58282, European organizations should implement several specific measures beyond generic advice: 1) Enforce strict local user privilege management on Huawei devices to minimize the number of users with low-level access capable of exploiting the vulnerability. 2) Educate users about the risks of social engineering or phishing attempts that could induce the required user interaction for exploitation. 3) Monitor device logs and behavior for unusual camera access patterns or unauthorized permission changes. 4) Restrict physical access to devices to prevent unauthorized local access. 5) Deploy mobile device management (MDM) solutions to enforce security policies and remotely manage permissions. 6) Stay informed about Huawei’s security advisories and apply patches promptly once available. 7) Consider disabling or restricting camera module access on devices where camera use is not essential. These targeted actions will reduce the attack surface and limit the vulnerability’s exploitation potential.

Description

Permission control vulnerability in the camera module. Successful exploitation of this vulnerability may affect service confidentiality.

Impact

For European organizations, the impact of CVE-2025-58282 is relatively low but non-negligible. Organizations using Huawei devices running the affected HarmonyOS versions could face confidentiality risks if an attacker gains local access to devices and successfully exploits the vulnerability. This could lead to unauthorized access to camera data or services, potentially exposing sensitive visual information or metadata. While the vulnerability does not compromise system integrity or availability, the breach of confidentiality could affect privacy compliance, especially under GDPR regulations. The requirement for local access and user interaction reduces the likelihood of widespread exploitation but does not eliminate insider threats or targeted attacks. Organizations with mobile workforces or those issuing Huawei devices to employees should be aware of this risk and monitor for suspicious local activity. The absence of known exploits in the wild suggests limited current threat but does not preclude future exploitation once the vulnerability becomes more widely known.

CWE-264Permissions, Privileges, and Access Controls (opens in a new tab)
CategoryOWASP Top 10 A01:2021: Broken Access Control (opens in a new tab)
Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.
MITRE does not allow mapping vulnerabilities to this entry; it groups weaknesses rather than naming one.

References

consumer.huawei.com/en/support/bulletin/2025/10/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Oct 2025, 01:04 UTC

WeaknessesCWE-264

Technical details

References

Community reviews

Related threats