Cyber Resilience

CVE-2025-54628

Huawei Harmonyos 4.0.0 … 5.1.0

Published
06 August 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0022 13th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-54628 is a medium-severity Range Error (CWE-118) vulnerability in Huawei Harmonyos. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Vulnerability of incomplete verification information in the communication module. Impact: Successful exploitation of this vulnerability may affect availability.

CWE(s)
CWE-118

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-46766Same product: Huawei Emui
CVE-2024-57961Same product: Huawei Emui
CVE-2023-46761Same product: Huawei Emui
CVE-2023-41307Same product: Huawei Emui
CVE-2024-47293Same product: Huawei Emui
CVE-2023-46770Same product: Huawei Emui
CVE-2023-46767Same product: Huawei Emui
CVE-2024-32998Same product: Huawei Emui
CVE-2023-52369Same product: Huawei Emui
CVE-2026-24919Same product: Huawei Emui

Affected Assets

huawei
emui
14.0.0, 15.0.0
huawei
harmonyos
4.0.0, 4.2.0, 4.3.0, 4.3.1, 5.0.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly stops out-of-bounds indices from being used on memory, arrays, or files.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles such as bounds checking and safe pointer arithmetic stop range errors from being introduced in code.

SC-39 Process Isolation partial match

Process isolation confines damage from an out-of-bounds access to a single domain without preventing the indexing flaw.

SI-16 Memory Protection partial match

Memory protection limits the blast radius of a successful range error but does not stop the incorrect access itself.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce bounds checking and input validation that prevent range errors.

DE.CM-09 partial match
prevents

Runtime monitoring can detect adverse events triggered by out-of-bounds accesses but does not prevent them.

ID.RA-01 partial match
prevents

Vulnerability identification processes can surface range-error flaws after they exist but do not stop their introduction.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect range errors through fuzzing and boundary-value analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes input validation and bounds checking that can prevent range errors.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate bounds checking and safe indexing practices.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote defensive coding that limits out-of-bounds access.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require bounds checking and safe array access to prevent range errors.

A.8.3 Information access restriction none match
none

Information access restriction limits who can access data but does not prevent index-based range errors within allowed access.

References