CVE-2025-26691

5.5 MEDIUM

📋 TL;DR

This vulnerability in OpenHarmony allows a local attacker to bypass permission checks and access sensitive information they shouldn't have access to. It affects OpenHarmony v5.0.3 and earlier versions. The attacker needs local access to the device to exploit this information leak.

💻 Affected Systems

Products:
  • OpenHarmony
Versions: v5.0.3 and prior versions
Operating Systems: OpenHarmony
Default Config Vulnerable: ⚠️ Yes
Notes: Affects OpenHarmony-based devices and systems using vulnerable versions. Requires local access to exploit.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Local attacker gains unauthorized access to sensitive system information, user data, or application data that should be protected by permissions.

🟠

Likely Case

Local user or malicious app accesses information from other apps or system components without proper authorization.

🟢

If Mitigated

With proper permission controls and isolation, impact is limited to information the attacker already has some legitimate access to.

🌐 Internet-Facing: LOW - This is a local vulnerability requiring attacker to have access to the device.
🏢 Internal Only: MEDIUM - Local attackers (including malicious apps) can exploit this to access sensitive information on the device.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires local access to the device. The vulnerability involves permission bypass to access information.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: OpenHarmony v5.0.4 or later

Vendor Advisory: https://gitee.com/openharmony/security/blob/master/zh/security-disclosure/2025/2025-06.md

Restart Required: Yes

Instructions:

1. Check current OpenHarmony version. 2. Update to OpenHarmony v5.0.4 or later. 3. Reboot the device after update. 4. Verify the update was successful.

🔧 Temporary Workarounds

Restrict local access

all

Limit physical and logical access to devices to trusted users only

Application isolation

all

Implement strict application sandboxing and permission controls

🧯 If You Can't Patch

  • Implement strict access controls to limit who can physically access devices
  • Monitor for suspicious local activity and permission bypass attempts

🔍 How to Verify

Check if Vulnerable:

Check OpenHarmony version: cat /etc/openharmony_version or equivalent system command

Check Version:

cat /etc/openharmony_version || getprop ro.build.version.ohos

Verify Fix Applied:

Verify version is v5.0.4 or later and test permission controls

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized permission requests
  • Access to protected resources without proper permissions
  • Permission bypass attempts in system logs

Network Indicators:

  • Not applicable - local vulnerability

SIEM Query:

Search for permission bypass events or unauthorized access to protected resources in system logs

🔗 References

📤 Share & Export