OpenHarmony up to 5.0.3 permissions

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in OpenHarmony up to 5.0.3. Impacted is an unknown function. Performing a manipulation results in permissions. This vulnerability was named CVE-2025-26691. The attack needs to be approached locally. There is no available exploit.

Detailsinfo

A vulnerability was found in OpenHarmony up to 5.0.3. It has been classified as problematic. This affects an unknown functionality. The manipulation with an unknown input leads to a permissions vulnerability. CWE is classifying the issue as CWE-281. The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended. This is going to have an impact on confidentiality. The summary by CVE is:

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.

The advisory is shared at gitee.com. This vulnerability is uniquely identified as CVE-2025-26691 since 03/02/2025. The exploitability is told to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-17390). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.4

VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 5.5
CNA Vector (OpenHarmony): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Permissions
CWE: CWE-281 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/02/2025 🔍
06/08/2025 +97 days 🔍
06/08/2025 +0 days 🔍
06/08/2025 +0 days 🔍

Sourcesinfo

Advisory: gitee.com
Status: Confirmed

CVE: CVE-2025-26691 (🔍)
GCVE (CVE): GCVE-0-2025-26691
GCVE (VulDB): GCVE-100-311613
EUVD: 🔍

Entryinfo

Created: 06/08/2025 15:26
Updated: 06/08/2025 15:53
Changes: 06/08/2025 15:26 (61), 06/08/2025 15:53 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!