CVE-2025-54644: Huawei HarmonyOS · Out-of-bounds Read
Affects Huawei HarmonyOSSource CVE Database V5
Not known to be exploited · CVSS 6.6 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.09% 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:L/PR:L/UI:N/S:U/C:L/I:L/A:HExploitation 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Huawei HarmonyOS | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation should focus on restricting local access to devices running affected HarmonyOS versions. Implement strict access controls and monitor for unauthorized local logins or suspicious activity. 2. Network segmentation should isolate Huawei HarmonyOS devices from critical infrastructure to limit the impact of potential exploitation. 3. Employ runtime protection and kernel integrity monitoring tools where possible to detect abnormal behavior or crashes related to the ambient light module. 4. Engage with Huawei support channels to obtain official patches or updates as soon as they become available and prioritize their deployment. 5. For organizations deploying HarmonyOS in IoT or embedded contexts, consider disabling or restricting the ambient light sensor module if feasible, reducing the attack surface. 6. Conduct regular vulnerability assessments and penetration testing focusing on local privilege escalation and kernel vulnerabilities to identify exploitation attempts. 7. Maintain comprehensive logging and alerting on devices to detect potential exploitation attempts early. 8. Educate internal teams about the risks of local access vulnerabilities and enforce policies minimizing unnecessary physical or local device access.
Description
Out-of-bounds array access issue due to insufficient data verification in the kernel ambient light module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.