CVE-2025-54606: Huawei HarmonyOS · Business Logic Errors
Affects Huawei HarmonyOSSource CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 26 Oct 2026, 06:26 UTC
- 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:N/S:U/C:H/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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Huawei HarmonyOS | Affected
| Fixed in– |
AI-suggested
Given the absence of an official patch, European organizations should implement several targeted mitigations: 1) Restrict physical and local access to HarmonyOS devices by enforcing strict device control policies and secure storage environments. 2) Employ mobile device management (MDM) solutions to monitor device status and enforce security configurations, including disabling unnecessary local interfaces that could be exploited. 3) Educate users on the risks of leaving devices unattended or accessible to unauthorized personnel. 4) Where feasible, isolate HarmonyOS devices from critical networks or sensitive data repositories until a patch is available. 5) Monitor for unusual device behavior or access attempts that could indicate exploitation attempts. 6) Engage with Huawei support channels to obtain timely updates or patches and apply them promptly once released. 7) Consider alternative device platforms for highly sensitive use cases until the vulnerability is resolved. These steps go beyond generic advice by focusing on access control, monitoring, and risk reduction specific to the local access vector and lock screen context of the vulnerability.
Description
Status verification vulnerability in the lock screen module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality.