VulnerabilityPublished 14 Jan 2026

CVE-2025-68956: Huawei HarmonyOS · Race Condition

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 8.0 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

8.0High

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% 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:H/A:H

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

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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jan 2026
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 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
HuaweiHarmonyOS	Affected =6.0.0	Fixed in–

AI-suggested

1. Monitor Huawei's official channels closely for patches addressing CVE-2025-68956 and apply them promptly once released. 2. Restrict local access to HarmonyOS devices by enforcing strict physical security controls and limiting administrative privileges. 3. Implement application whitelisting and endpoint protection to detect and prevent unauthorized local code execution. 4. Conduct thorough audits of multi-threaded applications and frameworks in use to identify and remediate synchronization issues proactively. 5. Deploy runtime monitoring tools capable of detecting anomalous behavior indicative of race condition exploitation, such as unexpected crashes or resource contention patterns. 6. Educate users and administrators about the risks of local access vulnerabilities and enforce policies to minimize exposure. 7. For critical environments, consider network segmentation to isolate vulnerable devices and reduce the attack surface. 8. Collaborate with Huawei and cybersecurity communities to share intelligence and best practices related to HarmonyOS security. These steps go beyond generic advice by focusing on access control, proactive detection, and vendor engagement specific to the nature of this race condition vulnerability.

Description

Multi-thread race condition vulnerability in the card framework module. Impact: Successful exploitation of this vulnerability may affect availability.

Impact

For European organizations, the exploitation of CVE-2025-68956 could lead to significant operational disruptions, particularly in environments where Huawei HarmonyOS devices are integrated into critical infrastructure or enterprise ecosystems. The availability impact could manifest as denial of service conditions, affecting user productivity and service continuity. Integrity impacts could result in corrupted data or malfunctioning applications dependent on the card framework, potentially undermining trust in device reliability. Confidentiality impact is lower but not negligible, as race conditions sometimes enable information leakage indirectly. Given the local access requirement, the threat is more pronounced in scenarios where devices are physically accessible or where attackers have gained local footholds, such as through insider threats or compromised endpoints. Organizations in sectors like telecommunications, manufacturing, and public services that utilize Huawei devices may face increased risk. The absence of known exploits provides a window for proactive mitigation, but the high CVSS score indicates that once exploited, the consequences could be severe. This vulnerability also raises concerns about supply chain security and device trustworthiness within European digital ecosystems.

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 02:27 UTC

WeaknessesCWE-362

Technical details

References

Community reviews

Related threats