Skip to main content
VulnerabilityPublished

CVE-2025-54652: 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

Immediate mitigation should focus on restricting local access to devices running affected HarmonyOS versions, enforcing strict user privilege management to minimize the risk of exploitation. Organizations should monitor for unusual file access patterns or virtualization module anomalies indicative of path traversal attempts. Employing application whitelisting and integrity monitoring on virtualization-related files can help detect unauthorized changes. Network segmentation to isolate vulnerable devices and limit lateral movement is advisable. Since no patches are currently linked, organizations should maintain close communication with Huawei for timely updates and apply patches as soon as they become available. Additionally, conducting thorough security audits of virtualization configurations and applying principle of least privilege to virtualization management interfaces can reduce exposure. For critical environments, consider temporary disabling or limiting virtualization features until a fix is deployed. Finally, educating users and administrators about the risks of local privilege misuse and enforcing strong endpoint security controls will help mitigate exploitation likelihood.

Description

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

References

Community reviews

Loading reviews…