CVE-2025-64313VulnerabilityPublished 28 Nov 2025

CVE-2025-64313: Huawei HarmonyOS · Race Condition

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.07% 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:U/C:L/I:L/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 28 Nov 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-25.

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 =5.0.1 =6.0.0	Fixed in–

AI-suggested

1. Monitor Huawei’s official security advisories closely for patches addressing CVE-2025-64313 and apply them promptly once available. 2. Restrict local access to devices running affected versions of HarmonyOS by enforcing strict physical and logical access controls, including multi-factor authentication and device lockdown policies. 3. Implement endpoint protection solutions capable of detecting anomalous process behavior or race condition exploitation attempts within office services. 4. Educate users about the risks of interacting with untrusted applications or processes that could trigger the race condition, reducing inadvertent exploitation. 5. Employ application whitelisting and privilege restrictions to limit the execution of unauthorized code that might exploit the vulnerability. 6. Conduct regular audits of device configurations and installed software versions to identify and remediate vulnerable systems. 7. Where possible, isolate critical office service environments from less trusted networks or user groups to minimize exposure. 8. Develop incident response plans that include detection and recovery procedures for denial of service events related to this vulnerability. These measures go beyond generic advice by focusing on access control, user awareness, and proactive monitoring tailored to the specific nature of the race condition vulnerability in HarmonyOS office services.

Description

CVE-2025-64313 is a medium-severity denial of service (DoS) vulnerability in Huawei HarmonyOS affecting versions 5.0.1, 5.1.0, and 6.0.0. It arises from a race condition (CWE-362) in the office service component due to improper synchronization of shared resources. Exploitation requires local access with low privileges and some user interaction, potentially causing service unavailability. No known public exploits exist yet.

Impact

For European organizations, the primary impact of CVE-2025-64313 is the potential denial of service of office services on devices running affected versions of Huawei HarmonyOS. This can disrupt business operations, particularly in environments where HarmonyOS devices are integrated into workflows or critical communication systems. The availability impact could lead to productivity loss, delayed communications, and potential cascading effects if the office service is part of larger automated processes. Confidentiality and integrity impacts are limited, reducing the risk of data breaches or unauthorized data modification. However, the disruption of services can affect operational continuity and user trust. Organizations relying on Huawei devices for office-related tasks should be aware of this risk, especially in sectors such as government, telecommunications, and enterprises with significant Huawei device deployments. The requirement for local access and user interaction reduces the likelihood of remote exploitation but does not eliminate insider threats or malware-based attacks. The absence of known exploits in the wild currently lowers immediate risk but emphasizes the importance of proactive mitigation.

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Architecture and Design
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design
Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design
Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Dec 2025, 04:33 UTC

WeaknessesCWE-362

Technical details

References

Community reviews

Related threats