CVE-2025-20063: OpenHarmony · Type Confusion
Affects OpenHarmonySource CVE Database V5
Not known to be exploited · CVSS 3.3 Low.
Data as of 26 Oct 2026, 06:26 UTC
- 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:LExploitation 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenHarmony OpenHarmony | Affected
| Fixed in– |
AI-suggested
1. Upgrade to the latest OpenHarmony version once patches addressing CVE-2025-20063 are released. Regularly monitor OpenHarmony security advisories for updates. 2. Restrict local access to devices running OpenHarmony to trusted users only, minimizing the risk of local attackers exploiting the vulnerability. 3. Implement application whitelisting and integrity checks to detect and prevent unauthorized or malformed applications that might trigger type confusion. 4. Employ runtime monitoring and anomaly detection on devices to identify unusual app crashes or behaviors indicative of exploitation attempts. 5. For critical deployments, consider sandboxing or isolating vulnerable applications to limit the impact of crashes on overall system availability. 6. Conduct regular security training for personnel managing OpenHarmony devices to recognize and respond to potential denial of service conditions caused by this vulnerability. 7. If possible, perform code audits or static analysis on custom applications running on OpenHarmony to detect and remediate type confusion issues proactively.
Description
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause apps crash through type confusion.