Skip to main content
VulnerabilityPublished Updated

CVE-2025-27242: OpenHarmony · Improper Input Validation

Affects OpenHarmonySource CVE Database V5

0

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% 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:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
OpenHarmony OpenHarmonyAffected
  • =5.0.1
  • <=5.0.3
Fixed in–

AI-suggested

To mitigate the risk posed by CVE-2025-27242, European organizations should implement the following specific measures: 1) Restrict physical and local access to devices running OpenHarmony to trusted personnel only, employing strong access control and monitoring. 2) Monitor devices for unusual behavior or crashes that could indicate exploitation attempts. 3) Maintain an inventory of all devices running OpenHarmony and track their versions to identify those affected by this vulnerability. 4) Engage with OpenHarmony project updates and security advisories to apply patches promptly once they become available. 5) Implement network segmentation to isolate IoT and smart devices from critical network segments, limiting the potential impact of a compromised device. 6) Conduct regular security training for staff to recognize and prevent unauthorized local access. 7) Where possible, deploy endpoint protection solutions capable of detecting anomalous local activities on IoT devices. These targeted actions go beyond generic advice by focusing on controlling local access and monitoring device behavior specific to the nature of this vulnerability.

Description

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through improper input.

References

Community reviews

Loading reviews…