VulnerabilityPublished 6 Aug 2025

CVE-2025-54645: Huawei HarmonyOS · Improper Validation of Array Index

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.0Medium

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

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:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within 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 =5.1.0 =5.0.1	Fixed in–

AI-suggested

To mitigate CVE-2025-54645, European organizations should take the following specific actions: 1) Inventory and identify all Huawei devices running HarmonyOS versions 5.0.1 or 5.1.0 within their environment, including mobile and IoT devices. 2) Restrict local access to these devices, enforcing strict physical security and limiting user permissions to reduce the risk of local exploitation. 3) Educate users about the risks of interacting with untrusted content or applications that could trigger the vulnerability, emphasizing caution with location service prompts or inputs. 4) Monitor Huawei's official channels for patches or firmware updates addressing this vulnerability and prioritize timely deployment once available. 5) Implement network segmentation to isolate IoT devices running HarmonyOS from critical infrastructure to contain potential denial of service impacts. 6) Employ endpoint detection and response (EDR) tools capable of detecting abnormal behavior or crashes related to location services on affected devices. 7) Consider alternative devices or operating systems for critical applications where feasible to reduce exposure. These targeted measures go beyond generic advice by focusing on device-specific controls, user awareness, and proactive patch management tailored to the nature of this vulnerability.

Description

Out-of-bounds array access issue due to insufficient data verification in the location service module. Impact: Successful exploitation of this vulnerability may affect availability.

Impact

For European organizations, the impact of CVE-2025-54645 depends largely on the extent of HarmonyOS device usage within their infrastructure or by their employees. Since HarmonyOS is primarily deployed on Huawei consumer devices and IoT products, enterprises using Huawei hardware for mobile or IoT purposes may face risks of service disruption or denial of service in location-based services. This could affect operational continuity, especially in sectors relying on precise location data such as logistics, transportation, or smart building management. Although the vulnerability does not directly compromise confidentiality or integrity, the potential for denial of service could disrupt critical workflows. Additionally, the changed scope (S:C) indicates that exploitation might affect other system components, potentially increasing the risk surface. Given the requirement for local access and user interaction, remote exploitation is unlikely without physical or local network access, somewhat limiting the threat to organizations with strict device control policies. However, in environments with BYOD policies or less controlled device usage, the risk is higher. The absence of known exploits suggests a window of opportunity for organizations to implement mitigations before active attacks emerge.

CWE-129Improper Validation of Array Index (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.
Architecture and Design · Input Validation
Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overflow Buffers (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:49 UTC

WeaknessesCWE-129

Technical details

References

Community reviews

Related threats