VulnerabilityPublished 5 Mar 2026

CVE-2026-28550: Huawei HarmonyOS · Business Logic Errors

Affects Huawei HarmonyOSSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.0 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

4.0Medium

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within 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 5 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
HuaweiHarmonyOS	Affected =6.0.0	Fixed in–

AI-suggested

To mitigate CVE-2026-28550, organizations should: 1) Monitor Huawei's official channels for patches or updates addressing this vulnerability and apply them promptly once available. 2) Restrict local access to devices running HarmonyOS 6.0.0 by enforcing strong physical security controls and limiting user privileges to reduce the risk of exploitation. 3) Implement runtime monitoring and anomaly detection to identify unusual process behavior indicative of race condition exploitation attempts. 4) Conduct thorough code reviews and testing for concurrency issues in custom applications or modules interacting with the security control module. 5) Employ application whitelisting and endpoint protection to prevent unauthorized code execution locally. 6) Educate users and administrators about the risks of local exploitation and the importance of maintaining device security hygiene. 7) Consider network segmentation to isolate critical HarmonyOS devices from less trusted networks or users. These measures go beyond generic advice by focusing on controlling local access, monitoring for concurrency anomalies, and preparing for patch deployment.

Description

Race condition vulnerability in the security control module. Impact: Successful exploitation of this vulnerability may affect availability.

Impact

The primary impact of CVE-2026-28550 is on system availability, potentially allowing attackers with local access to cause denial of service conditions on devices running HarmonyOS 6.0.0. This could disrupt critical services or user operations, particularly in environments relying on Huawei devices for communication, IoT, or enterprise applications. While confidentiality and integrity are not directly affected, availability disruptions can have cascading effects, including loss of productivity, interruption of business processes, and potential safety risks in industrial or critical infrastructure contexts. Since exploitation requires local access, the threat is more relevant to insider threats, compromised devices, or scenarios where attackers gain physical or remote local access. The lack of known exploits reduces immediate risk, but the vulnerability could be leveraged in targeted attacks or combined with other exploits for greater impact. Organizations deploying HarmonyOS devices should consider the operational risks of availability loss and the potential for service interruptions in sensitive environments.

CWE-840Business Logic Errors (opens in a new tab)
CategoryOWASP Top 10 A04:2021: Insecure Design (opens in a new tab)
Weaknesses in this category identify some of the underlying problems that commonly allow attackers to manipulate the business logic of an application. Errors in business logic can be devastating to an entire application. They can be difficult to find automatically, since they typically involve legitimate use of the application's functionality. However, many business logic errors can exhibit patterns that are similar to well-understood implementation and design weaknesses.
MITRE does not allow mapping vulnerabilities to this entry; it groups weaknesses rather than naming one.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Mar 2026, 08:17 UTC

WeaknessesCWE-840

Technical details

References

Community reviews

Related threats