CVE-2025-24493: OpenHarmony · Race Condition
Affects OpenHarmonySource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% 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:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jun 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenHarmony OpenHarmony | Affected
| Fixed in– |
AI-suggested
Organizations should prioritize upgrading OpenHarmony installations to versions beyond 5.0.3 once patches become available. Until then, they should implement strict access controls to limit local user access to trusted personnel only, minimizing the risk of exploitation. Employing runtime monitoring and anomaly detection on devices can help identify suspicious concurrent access patterns indicative of exploitation attempts. Additionally, organizations should audit and harden device configurations to reduce unnecessary local access interfaces (e.g., disabling unused local shells or debug ports). For environments where OpenHarmony devices are deployed, network segmentation and endpoint protection can limit lateral movement if a local compromise occurs. Finally, maintaining an inventory of all OpenHarmony devices and tracking their firmware versions will facilitate timely patch management once fixes are released.
Description
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through race condition.