CVE-2025-66323VulnerabilityPublished 8 Dec 2025

CVE-2025-66323: Huawei HarmonyOS · Improperly Implemented Security Check for Standard

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.3Medium

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: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 8 Dec 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 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 and apply patches promptly once released to address CVE-2025-66323. 2. Restrict local access to HarmonyOS devices by enforcing strong physical security controls and limiting user privileges to reduce the risk of exploitation. 3. Educate users about the risks of social engineering and the importance of not interacting with untrusted prompts or applications that could trigger the vulnerability. 4. Implement endpoint protection solutions capable of detecting suspicious local activities or attempts to exploit system modules. 5. Conduct regular security audits and vulnerability assessments on devices running HarmonyOS to identify and remediate potential weaknesses. 6. For organizations deploying HarmonyOS in critical environments, consider network segmentation and device isolation to contain potential impacts. 7. Maintain up-to-date backups and incident response plans to quickly recover from availability disruptions. 8. Collaborate with Huawei support channels for guidance and early access to patches or mitigations if available.

Description

Vulnerability of improper criterion security check in the card module. Impact: Successful exploitation of this vulnerability may affect availability.

Impact

For European organizations, the primary impact of CVE-2025-66323 lies in potential availability disruptions on devices running affected versions of HarmonyOS. This could translate into denial-of-service conditions or degraded device performance, impacting user productivity and operational continuity. Confidentiality and integrity impacts are assessed as low, reducing risks of data breaches or unauthorized data modification. However, organizations relying on HarmonyOS for critical communications or operations may experience interruptions. The requirement for local access and user interaction limits the threat to scenarios involving insider threats, compromised endpoints, or social engineering attacks. The absence of known exploits reduces immediate risk but underscores the need for proactive mitigation. Given Huawei's significant market presence in certain European countries, especially in telecommunications and consumer devices, the vulnerability could affect sectors such as government, telecommunications, and enterprises using Huawei hardware or software. The medium severity rating suggests moderate urgency in addressing the vulnerability to prevent potential service disruptions.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Dec 2025, 08:20 UTC

WeaknessesCWE-358

Technical details

References

Community reviews

Related threats