Skip to main content

OpenHarmony CVE-2026-24792

| EUVDEUVD-2026-30826 HIGH
Signal Handler Race Condition (CWE-364)
2026-05-19 OpenHarmony GHSA-mv6m-pvcq-372p
8.1
CVSS 3.1 · Vendor: OpenHarmony
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privilege device credentials
  2. Delivery
    Identify exposed pre-installed app service
  3. Exploit
    Send crafted network request
  4. Execution
    Win signal handler race condition
  5. Impact
    Execute 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

OpenHarmony v5.0.3 ≤v6.0

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

Vendor (OpenHarmony) PRIMARY 8.1 HIGH
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

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

DescriptionCVE.org

in OpenHarmony v6.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps.

Executive ViewAI

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.2%
Top 60% exploitable
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2024-37185 CRITICAL
9.8 Jul 02

in OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through

CVE-2024-37077 CRITICAL
9.8 Jul 02

in OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through

CVE-2024-37030 CRITICAL
9.8 Jul 02

in OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through

CVE-2024-36260 CRITICAL
9.8 Jul 02

in OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through

CVE-2024-36243 CRITICAL
9.8 Jul 02

in OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through

CVE-2025-0303 HIGH
8.8 Feb 07

in OpenHarmony v4.1.2 and prior versions allow a local attacker cause the common permission is upgraded to root and sens

CVE-2024-29074 HIGH
8.8 Apr 02

in OpenHarmony v3.2.4 and prior versions allow a local attacker arbitrary code execution in any apps through improper in

CVE-2024-22098 HIGH
8.8 Apr 02

in OpenHarmony v3.2.4 and prior versions allow a local attacker arbitrary code execution in any apps through use after f

CVE-2024-21860 HIGH
8.8 Feb 02

in OpenHarmony v4.0.0 and prior versions allow an adjacent attacker arbitrary code execution in any apps through use aft

CVE-2022-42463 HIGH
8.8 Oct 14

OpenHarmony-v3.1.2 and prior versions have an authenication bypass vulnerability in a callback handler function of Softb

CVE-2022-38700 HIGH
8.8 Sep 09

OpenHarmony-v3.1.1 and prior versions have a permission bypass vulnerability. Rated high severity (CVSS 8.8), this vulne

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy