Skip to main content
VulnerabilityPublished

CVE-2025-54653: Huawei HarmonyOS · Path Traversal

Affects Huawei HarmonyOSSource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.4High
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:L/UI:N/S:C/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
Huawei HarmonyOSAffected
  • =5.0.2
  • =5.0.1
Fixed in–

AI-suggested

  1. Immediate upgrade: Organizations should prioritize upgrading HarmonyOS to a patched version once Huawei releases a fix. Until then, restrict access to systems running affected versions (5.0.1 and 5.0.2) to trusted users only.
  2. Access controls: Implement strict access control policies limiting user privileges on devices running HarmonyOS, especially restricting access to virtualization file modules.
  3. Network segmentation: Isolate HarmonyOS devices within segmented network zones to limit lateral movement in case of exploitation.
  4. Monitoring and detection: Deploy file integrity monitoring and anomaly detection tools focused on virtualization file system activities to detect suspicious path traversal attempts.
  5. Virtualization hardening: Harden virtualization environments by applying best practices such as limiting file system permissions, disabling unnecessary services, and enforcing strict container or VM isolation.
  6. Incident response readiness: Prepare incident response plans specific to virtualization compromise scenarios, including forensic capabilities to analyze potential data exfiltration or service disruption.
  7. Vendor engagement: Maintain close communication with Huawei for timely patch releases and security advisories related to this vulnerability.

Description

Path traversal vulnerability in the virtualization file module. Successful exploitation of this vulnerability may affect the confidentiality of the virtualization file module.

References

Community reviews

Loading reviews…