CVE-2025-58315VulnerabilityPublished 28 Nov 2025

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

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.5Medium

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:N/UI:R/S:U/C:N/I:N/A:H

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Nov 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 2026-10-25.

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 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 =6.0.0	Fixed in–

AI-suggested

1. Monitor Huawei’s official security advisories for patches addressing CVE-2025-58315 and apply updates promptly once available. 2. Restrict physical and local network access to devices running HarmonyOS, especially in sensitive or high-security environments, to reduce the risk of local exploitation. 3. Implement strict user access controls and educate users about the risks of interacting with untrusted applications or prompts that could trigger the vulnerability. 4. Employ network segmentation to isolate HarmonyOS devices from critical network segments to limit potential impact of service disruption. 5. Use endpoint detection and response (EDR) tools to monitor for unusual local activity that could indicate attempts to exploit local vulnerabilities. 6. Conduct regular audits of device configurations and permissions to ensure adherence to the principle of least privilege. 7. Prepare incident response plans that include scenarios involving denial of service on critical connectivity modules.

Description

CVE-2025-58315 is a medium severity permission control vulnerability in the Wi-Fi module of Huawei's HarmonyOS versions 5.0.1, 5.1.0, and 6.0.0. The flaw relates to improper permissions and access controls (CWE-264), potentially allowing unauthorized local attackers to disrupt service availability. Exploitation requires local access and user interaction but does not impact confidentiality or integrity directly. No known exploits are currently reported in the wild.

Impact

For European organizations, the primary impact of CVE-2025-58315 is the potential disruption of Wi-Fi services on devices running affected versions of HarmonyOS. This could lead to temporary loss of network connectivity, affecting business operations reliant on these devices for communication or IoT functions. Although confidentiality and integrity are not directly impacted, availability degradation can interrupt workflows, especially in environments where HarmonyOS-powered devices are integrated into enterprise networks or critical infrastructure. The requirement for local access and user interaction limits the attack surface, reducing risk from remote attackers but increasing concern in scenarios where devices are physically accessible by unauthorized personnel. Organizations using Huawei devices in sensitive or operational technology contexts should be aware of this vulnerability as it could be leveraged in targeted attacks to cause service outages. The absence of known exploits reduces immediate risk but does not eliminate the need for proactive mitigation.

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/11/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Dec 2025, 04:32 UTC

WeaknessesCWE-264

Technical details

References

Community reviews

Related threats