CVE-2025-54649: Huawei HarmonyOS · Type Confusion
Affects Huawei HarmonyOSSource CVE Database V5
Not known to be exploited · CVSS 4.5 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- 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:H/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Huawei HarmonyOS | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations using Huawei HarmonyOS devices should: 1) Monitor Huawei's official security advisories and promptly apply any patches or updates once available to address CVE-2025-54649. 2) Restrict physical and local access to devices running affected versions to trusted personnel only, minimizing the risk of local exploitation. 3) Implement strict device management policies, including the use of Mobile Device Management (MDM) solutions that can enforce security configurations and monitor device integrity. 4) For critical applications relying on location data, implement validation and cross-verification mechanisms to detect anomalies or inconsistencies in location information. 5) Educate users and administrators about the risks of local exploitation and encourage reporting of suspicious device behavior. 6) Consider network segmentation and access controls to limit exposure of devices with vulnerable HarmonyOS versions within corporate networks. 7) If feasible, evaluate the possibility of upgrading to newer HarmonyOS versions or alternative platforms not affected by this vulnerability.
Description
Vulnerability of using incompatible types to access resources in the location service. Impact: Successful exploitation of this vulnerability may cause some location information attributes to be incorrect.