VulnerabilityPublished 6 Aug 2025

CVE-2025-54628: Huawei HarmonyOS · Range Error

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Huawei HarmonyOS	Affected 4.0.0 – 5.1.0 6 affected builds	Fixed in–

AI-suggested

Given the vulnerability arises from incomplete verification in the communication module, European organizations should implement the following specific mitigations: 1) Inventory and identify all Huawei devices running affected versions of HarmonyOS (4.0.0 through 5.1.0) within their environment, including smartphones, IoT endpoints, and embedded systems. 2) Monitor Huawei's official security advisories and update channels closely for the release of patches addressing CVE-2025-54628, and plan for rapid deployment once available. 3) Employ network-level protections such as intrusion detection/prevention systems (IDS/IPS) configured to detect anomalous or malformed packets targeting HarmonyOS communication protocols, potentially blocking exploit attempts. 4) Segment networks to isolate critical HarmonyOS devices from untrusted or less secure network zones, reducing exposure to remote attacks. 5) Implement rate limiting and traffic filtering on communication interfaces to mitigate potential denial-of-service attempts exploiting the range error. 6) Conduct security awareness and training for IT staff to recognize symptoms of device instability or crashes that may indicate exploitation attempts. 7) Engage with Huawei support for guidance on interim workarounds or configuration changes that may reduce attack surface until patches are released. 8) Consider deploying endpoint protection solutions capable of monitoring device health and alerting on abnormal behavior related to communication module failures. These targeted actions go beyond generic advice by focusing on device identification, network controls specific to communication modules, and proactive monitoring tailored to the nature of this vulnerability.

Description

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

Impact

For European organizations, the impact of CVE-2025-54628 primarily concerns the availability of devices running Huawei's HarmonyOS. This OS is used in a variety of Huawei products, including smartphones, IoT devices, and potentially embedded systems in enterprise environments. Disruption of availability can lead to denial-of-service scenarios, affecting business operations reliant on these devices. In sectors such as telecommunications, manufacturing, and smart infrastructure where HarmonyOS-powered devices may be integrated, service interruptions could result in operational delays, reduced productivity, and potential financial losses. Additionally, organizations using HarmonyOS devices for critical communication or control functions may face increased risk of downtime. Although the vulnerability does not compromise confidentiality or integrity, the availability impact can indirectly affect compliance with service-level agreements (SLAs) and regulatory requirements related to operational resilience. The lack of required privileges or user interaction for exploitation increases the risk profile, as attackers can remotely target vulnerable devices without needing to compromise user credentials or trick users into action. However, the absence of known exploits in the wild and the medium severity rating suggest that the immediate threat level is moderate, but organizations should remain vigilant and prepare to apply mitigations promptly once patches become available.

CWE-118Incorrect Access of Indexable Resource ('Range Error') (opens in a new tab)
Class weakness
The product does not restrict or incorrectly restricts operations within the boundaries of a resource that is accessed using an index or pointer, such as memory or files.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
Buffer Overflow via Symbolic Links (opens in a new tab)
Overflow Variables and Tags (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

consumer.huawei.com/en/support/bulletin/2025/8/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2025, 03:05 UTC

WeaknessesCWE-118

Technical details

References

Community reviews

Related threats