CVE-2025-54621VulnerabilityPublished 6 Aug 2025

CVE-2025-54621: Huawei HarmonyOS · Improper Control of a Resource Through its Lifetime

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

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

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:L

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

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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: 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: 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 2026-10-26.

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 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	Fixed in–

AI-suggested

To mitigate CVE-2025-54621, European organizations should first inventory all Huawei devices running HarmonyOS 5.1.0 within their environment. Since no official patches are currently linked, organizations should monitor Huawei’s security advisories closely for updates or patches addressing this issue. In the interim, restricting local access to devices is critical; this includes enforcing strict physical security controls, limiting user privileges, and employing endpoint protection solutions that can detect anomalous local activities. Network segmentation should be applied to isolate Huawei devices from critical infrastructure to reduce the risk of lateral movement if a device is compromised. Additionally, organizations should implement runtime monitoring to detect unusual memory usage patterns or device instability that could indicate exploitation attempts. For developers or integrators using HarmonyOS in custom solutions, reviewing and hardening the management of resource lifetimes in the WantAgent module or related components is advisable. Finally, organizations should consider alternative devices or OS versions if the risk profile is unacceptable, especially in high-security environments.

Description

Iterator failure issue in the WantAgent module. Impact: Successful exploitation of this vulnerability may cause memory release failures.

Impact

For European organizations, the impact of CVE-2025-54621 depends largely on their use of Huawei devices running HarmonyOS 5.1.0. Enterprises and service providers that deploy Huawei smartphones, IoT devices, or embedded systems in their infrastructure could face risks of degraded device performance or stability issues due to memory release failures. This could lead to intermittent outages or reduced reliability of critical systems, especially in environments relying on Huawei hardware for communications or IoT management. Although the vulnerability does not currently have known exploits in the wild, the local access requirement means that attackers would need some level of access to the device, which could be achieved through insider threats or other local compromise vectors. The limited impact on confidentiality, integrity, and availability suggests that while the vulnerability is not catastrophic, it could be leveraged as part of a multi-stage attack chain. In sectors such as telecommunications, manufacturing, or smart city infrastructure where Huawei devices are prevalent, this vulnerability could disrupt operations or provide footholds for attackers. Additionally, given the geopolitical sensitivity around Huawei products in Europe, organizations might face increased scrutiny or regulatory pressure to address such vulnerabilities promptly.

CWE-664Improper Control of a Resource Through its Lifetime (opens in a new tab)
Pillar weakness
The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Attack patterns
Session Credential Falsification through Forging (opens in a new tab)
Reusing Session IDs (aka Session Replay) (opens in a new tab)
Session Fixation (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
Exploitation of Trusted Identifiers (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, 02:36 UTC

WeaknessesCWE-664

Technical details

References

Community reviews

Related threats