Openharmony Vulnerabilities

Security vulnerability tracking for Openatom Openharmony

Last updated: Mar 16, 2026
Total CVEs

3

Critical

0

With Exploits

3

Last 30 Days

5

Vulnerability Timeline

3 vulnerabilities discovered over time for Openharmony

Severity Distribution

Critical0
0%
High3
100%
Medium1
33%
Low1
33%
DescriptionVendor / ProductExploit Status
CVE-2025-524587.8

This vulnerability allows a local attacker to run their own code within pre-installed apps on OpenHarmony devices, potentially leading to unauthorized access or control. However, it can only be exploited in specific situations where the attacker has local access to the device.

openatomopenharmony
Theoretical
23 days agoMar 16, 2026
CVE-2025-414327.8

This vulnerability allows a local attacker to run any code they want in pre-installed apps on OpenHarmony devices, which could lead to unauthorized actions or data access. However, the attack can only happen in specific situations where the attacker has physical access to the device.

openatomopenharmony
Exploit Available
23 days agoMar 16, 2026
CVE-2025-252777.0

This vulnerability allows a local attacker to run their own code within pre-installed apps on OpenHarmony devices, potentially taking control of those apps. However, it can only be exploited in specific situations where the attacker has access to the device.

openatomopenharmony
Exploit Available
23 days agoMar 16, 2026

About Openatom Openharmony Security

This page provides comprehensive security vulnerability tracking for Openatom Openharmony. Our database includes all CVEs affecting this product, updated in real-time from official sources.

Each vulnerability listing includes detailed CVSS severity analysis, exploit availability status, AI-generated explanations, and direct links to official security patches and vendor advisories.

Security Recommendations

  • • Always keep Openharmony updated to the latest version
  • • Subscribe to security advisories from Openatom
  • • Monitor this page for new vulnerabilities affecting your version
  • • Prioritize patching critical and high severity issues immediately