Skip to main content
CVE-2025-27131VulnerabilityPublished

CVE-2025-27131: OpenHarmony · Improper Input Validation

Affects OpenHarmonySource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% 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:H/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 2026-10-25.

What to do

Affected software

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

AI-suggested

To mitigate CVE-2025-27131 effectively, European organizations should: 1) Inventory and identify all devices running OpenHarmony v5.0.3 or earlier, focusing on version 5.0.1. 2) Restrict local access to these devices by enforcing strict physical security controls and network segmentation to limit exposure to untrusted users or systems. 3) Monitor device behavior for signs of abnormal crashes or service interruptions that could indicate exploitation attempts. 4) Engage with OpenHarmony vendors or community to obtain patches or updates addressing this vulnerability as soon as they become available. 5) Implement application whitelisting and integrity verification mechanisms on devices where feasible to detect unauthorized input or code execution attempts. 6) Conduct regular security audits and penetration testing focusing on input validation and local access controls of embedded devices. 7) Educate staff on the risks of local access exploitation and enforce policies to minimize insider threat risks. These steps go beyond generic advice by emphasizing device inventory, physical and network access controls, behavioral monitoring, and proactive engagement with vendor updates.

Description

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

References

Community reviews

Loading reviews…