VulnerabilityPublished 6 Aug 2025

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

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.9Medium

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
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: 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: 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 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	Fixed in–

AI-suggested

To mitigate this vulnerability effectively, European organizations should: 1) Prioritize updating HarmonyOS devices to patched versions once Huawei releases a fix, monitoring official Huawei security advisories closely. 2) Restrict physical and local access to devices running HarmonyOS 5.1.0, implementing strict endpoint security controls and device management policies. 3) Employ application whitelisting and endpoint detection and response (EDR) solutions to detect and prevent unauthorized local code execution that could exploit this vulnerability. 4) Conduct regular security audits and vulnerability assessments on Huawei devices within their environment to identify any anomalous behavior linked to the card management module. 5) For critical deployments, consider network segmentation and isolation of Huawei HarmonyOS devices to limit lateral movement in case of compromise. 6) Educate IT and security staff about the vulnerability and the importance of monitoring device stability and logs for signs of exploitation attempts. These steps go beyond generic patching advice by emphasizing access control, monitoring, and proactive detection tailored to the local attack vector nature of this vulnerability.

Description

Iterator failure vulnerability in the card management module. Impact: Successful exploitation of this vulnerability may affect function stability.

Impact

For European organizations utilizing Huawei devices running HarmonyOS 5.1.0, particularly those relying on the card management module (which may be involved in SIM card management or other secure element interactions), this vulnerability could lead to instability in critical functions. While the direct impact on confidentiality and integrity is low, the availability and reliability of services could be compromised, potentially disrupting business operations or communications. This is especially relevant for telecom operators, enterprises using Huawei-based IoT devices, or mobile endpoints within corporate environments. Given the local access requirement, the threat is more significant in scenarios where devices are physically accessible by attackers or where malware could gain local execution privileges. The absence of known exploits reduces immediate risk but does not eliminate the possibility of future exploitation. Disruptions caused by this vulnerability could affect service continuity, leading to operational downtime or degraded user experience, which in regulated sectors such as finance or critical infrastructure could have compliance and reputational consequences.

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:49 UTC

WeaknessesCWE-664

Technical details

References

Community reviews

Related threats