CVE-2025-58288VulnerabilityPublished 11 Oct 2025Updated 14 Oct 2025

CVE-2025-58288: Huawei HarmonyOS · Permission Issues

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.08% 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 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 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	Fixed in–

AI-suggested

1. Restrict physical and local access to Huawei HarmonyOS devices, especially in sensitive or high-risk environments, to reduce the likelihood of exploitation. 2. Educate users about the risks of interacting with unexpected prompts or actions on their devices to mitigate user interaction requirements. 3. Implement strict device usage policies and monitor for unusual behavior or service disruptions related to the office service component. 4. Employ endpoint detection and response (EDR) tools capable of identifying anomalous local activities on HarmonyOS devices. 5. Prepare for timely deployment of patches or updates from Huawei once they become available; maintain close communication with Huawei security advisories. 6. Consider network segmentation to isolate critical HarmonyOS devices from less trusted networks or users. 7. Conduct regular audits of device permissions and configurations to ensure no excessive privileges are granted to office service components. 8. Develop incident response plans that include scenarios involving denial of service on critical office services to minimize downtime and impact.

Description

Denial of service (DoS) vulnerability in the office service. Successful exploitation of this vulnerability may affect availability.

Impact

For European organizations, the primary impact of CVE-2025-58288 is the potential disruption of availability in office services running on Huawei HarmonyOS devices. This can lead to operational downtime, reduced productivity, and potential business continuity challenges, especially in sectors heavily reliant on mobile or embedded HarmonyOS devices for office-related tasks. Although confidentiality and integrity are not affected, the denial of service could impair communication, document processing, and other critical office functions. Organizations in industries such as telecommunications, government, and technology that utilize Huawei devices may experience more pronounced effects. The requirement for local access and user interaction somewhat limits the threat scope but does not eliminate risk in environments where devices are shared or physically accessible. Additionally, the absence of patches increases exposure until a fix is available. The impact is heightened in environments with limited device management or where users may be susceptible to social engineering tactics to trigger the vulnerability.

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:05 UTC

WeaknessesCWE-275

Technical details

References

Community reviews

Related threats