Skip to main content
VulnerabilityPublished

CVE-2025-21082: OpenHarmony · Type Confusion

Affects OpenHarmonySource CVE Database V5

0

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 14:05 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

2) Restrict local access to devices running OpenHarmony by enforcing strict physical security controls and network segmentation to minimize the risk of local attackers. 3) Implement application whitelisting and integrity monitoring on OpenHarmony devices to detect abnormal application crashes or suspicious behavior indicative of exploitation attempts. 4) Conduct regular audits of user privileges on devices to ensure that only trusted users have local access, reducing the attack surface. 5) For critical deployments, consider deploying additional monitoring tools that can detect and alert on application crashes or unusual system behavior to enable rapid response. 6) Engage with device vendors to confirm the use of OpenHarmony versions and coordinate vulnerability management efforts. These steps go beyond generic advice by focusing on access control, monitoring, and vendor coordination specific to the nature of this vulnerability.

Description

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause apps crash through type confusion.

References

Community reviews

Loading reviews…