Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege device credentials
-
DeliveryIdentify exposed pre-installed app service
-
ExploitSend crafted network request
-
ExecutionWin signal handler race condition
-
ImpactExecute arbitrary code in app context
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Exploitation requires network reachability to an OpenHarmony device running version 6.0 or earlier and low-privilege authentication credentials (PR:L) on the target, with the vulnerable pre-installed app's service endpoint exposed and reachable to the attacker. The vulnerability is a CWE-364 signal handler race condition, so successful exploitation depends on winning a timing race during signal handling within the targeted pre-installed application's process - though the CVSS vector claims AC:L, race condition exploitation typically requires repeated attempts or specific timing conditions. No user interaction is required (UI:N), and the scope is unchanged (S:U), meaning the attacker gains code execution only within the privileges of the affected pre-installed app rather than escalating beyond it. Limiting factors include the authenticated access requirement and the need for the vulnerable pre-installed app to be present and reachable on the device. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H indicates network-reachable exploitation with low complexity by an authenticated attacker with low privileges, yielding high confidentiality and availability impact but notably no integrity impact - an unusual profile for an RCE claim that warrants scrutiny. EPSS and KEV data were not provided in the input, and no public exploit has been identified, so real-world exploitation pressure cannot be quantified from available signals. The combination of CWE-364 (race condition) with AC:L is somewhat contradictory, as race conditions typically exhibit timing-dependent reliability that would suggest AC:H - defenders should verify the attack complexity claim with the vendor. The 'remote attacker' wording in the description combined with AV:N suggests network-exposed pre-installed app services, but the specific service surface is not documented in the provided sources. |
| Exploit ScenarioDerived | An attacker who has obtained low-privilege credentials on an OpenHarmony 6.0 device - for example through a compromised user account or a companion app token - sends crafted network requests to a vulnerable pre-installed application, triggering the signal handler race condition (CWE-364) during signal processing. By winning the race, the attacker hijacks execution flow within the pre-installed app's process context, gaining arbitrary code execution on the device. No public proof-of-concept has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 19, 2026
Remote code execution in OpenHarmony v6.0 and prior versions allows authenticated remote attackers to execute arbitrary code within pre-installed applications through a race condition flaw (CWE-364). The CVSS 8.1 score reflects high confidentiality and availability impact but no integrity impact, and no public exploit has been identified at time of analysis. The vulnerability requires low privileges but no user interaction, making it exploitable across OpenHarmony's distributed device ecosystem including smart devices, wearables, and IoT endpoints running the open-source operating system.
RemediationAI
Patch availability is referenced via the OpenHarmony security disclosure at https://gitcode.com/openharmony/security/tree/master/zh/security-disclosure/2026/2026-04.md, but a specific fixed version is not stated in the provided data, so consult that advisory for the exact patched release and upgrade affected devices accordingly. As compensating controls until patching is feasible, restrict network exposure of OpenHarmony devices by placing them behind segmented VLANs or firewalls that block untrusted ingress to device service ports, and limit the set of accounts able to authenticate locally or remotely since PR:L exploitation requires at least low-privilege credentials. Where pre-installed apps with network services are not required, disabling those specific services reduces the attack surface, with the trade-off being loss of associated functionality such as remote management or device-to-device interaction.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
OpenHarmony is an open-source distributed operating system developed under the OpenAtom Foundation, designed for smart devices, IoT endpoints, and consumer electronics across multiple form factors. The affected CPE cpe:2.3:a:openharmony:openharmony covers all OpenHarmony releases up to and including v6.0. The root cause is classified as CWE-364 (Signal Handler Race Condition), which arises when a signal handler accesses shared state that can be concurrently modified, creating a window where an attacker can manipulate program flow during the non-atomic handling of asynchronous signals. In the context of pre-installed apps, this likely affects privileged system components or framework services that handle inter-process communication or system signals, enabling unexpected code paths to be triggered during the race window.
Know when Openharmony gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Primary rating from Vendor (OpenHarmony) · only source for this CVE.
CVSS VectorVendor: OpenHarmony
DescriptionCVE.org
in OpenHarmony v6.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps.
Executive ViewAI
A remote code execution vulnerability in OpenHarmony v6.0 and earlier versions affects authenticated users across distributed device ecosystems including smart devices and IoT endpoints, creating elevated risk for organizations with OpenHarmony deployments lacking compensating controls. With no vendor-released patch identified at time of analysis, enterprises must prioritize inventory and network segmentation to limit exposure across their device fleet. The vulnerability enables attackers with authenticated access and low privileges to execute arbitrary code, compromising confidentiality and availability of affected systems.
Until vendor patch is released: segment OpenHarmony systems to restricted network enclaves with no lateral movement to critical assets, enforce principle of least privilege for authenticated user accounts, implement runtime behavior monitoring to detect arbitrary code execution in pre-installed applications, require approval workflows for any user authentication to OpenHarmony systems, and maintain immutable audit logs of all authenticated access and application execution events.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Related Vulnerabilities in OpenHarmony Memory Corruption and Access Flaws
View all 10More in Openharmony
View allin OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through
in OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through
in OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through
in OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through
in OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through
in OpenHarmony v4.1.2 and prior versions allow a local attacker cause the common permission is upgraded to root and sens
in OpenHarmony v3.2.4 and prior versions allow a local attacker arbitrary code execution in any apps through improper in
in OpenHarmony v3.2.4 and prior versions allow a local attacker arbitrary code execution in any apps through use after f
in OpenHarmony v4.0.0 and prior versions allow an adjacent attacker arbitrary code execution in any apps through use aft
OpenHarmony-v3.1.2 and prior versions have an authenication bypass vulnerability in a callback handler function of Softb
OpenHarmony-v3.1.1 and prior versions have a permission bypass vulnerability. Rated high severity (CVSS 8.8), this vulne
EUVD-2026-30826
GHSA-mv6m-pvcq-372p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB