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

CVE-2025-58286: Huawei HarmonyOS · Path Traversal: '/../filedir'

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.3Low

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% 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:L

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

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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 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 local access to HarmonyOS devices, ensuring only trusted users can interact with the office service. 2. Implement strict user privilege management to minimize unnecessary access rights, reducing the risk of unauthorized local exploitation. 3. Monitor logs and system behavior for unusual file path access patterns or repeated failures in the office service that may indicate exploitation attempts. 4. Educate users about the risks of interacting with untrusted content or applications that might trigger the vulnerability. 5. Apply network segmentation to isolate HarmonyOS devices from critical infrastructure to limit impact in case of a DoS event. 6. Stay updated with Huawei security advisories and apply patches promptly once available. 7. Consider deploying endpoint detection and response (EDR) solutions capable of detecting anomalous file system activities related to path traversal attempts. 8. Conduct regular security audits and vulnerability assessments on HarmonyOS deployments to identify and remediate potential exposure.

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-58286 is the potential disruption of availability in systems running Huawei HarmonyOS office services. This could affect business continuity, especially in environments relying on HarmonyOS devices for office productivity or critical workflows. While confidentiality and integrity are not compromised, denial of service conditions can lead to operational delays and reduced productivity. Organizations with Huawei device deployments in sectors such as telecommunications, government, or enterprises using HarmonyOS may face increased risk. The requirement for local access and user interaction reduces the likelihood of widespread exploitation but does not eliminate insider threat or targeted attack scenarios. In critical infrastructure or sensitive environments, even low-severity availability disruptions can have cascading effects. Therefore, European entities should assess their exposure based on device usage and implement controls to minimize local exploitation opportunities.

CWE-25Path Traversal: '/../filedir' (opens in a new tab)
Variant weakness
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/../" sequences that can resolve to a location that is outside of that directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

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-25

Technical details

References

Community reviews

Related threats