| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenHarmony up to 5.0.3.x. It has been declared as problematic. Impacted is an unknown function. Such manipulation leads to input validation. This vulnerability is traded as CVE-2025-26474. An attack has to be approached locally. There is no exploit available.
Details
A vulnerability was found in OpenHarmony up to 5.0.3.x. It has been rated as problematic. Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality. CVE summarizes:
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information improper input. This vulnerability can be exploited only in restricted scenarios.
The advisory is shared for download at gitcode.com. This vulnerability is handled as CVE-2025-26474 since 03/02/2025. The exploitation is known to be easy. The attack needs to be approached locally. There are neither technical details nor an exploit publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.3
CNA Vector (OpenHarmony): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/02/2025 CVE reserved03/16/2026 Advisory disclosed
03/16/2026 VulDB entry created
03/20/2026 VulDB entry last update
Sources
Advisory: gitcode.comStatus: Confirmed
CVE: CVE-2025-26474 (🔒)
GCVE (CVE): GCVE-0-2025-26474
GCVE (VulDB): GCVE-100-351224
Entry
Created: 03/16/2026 10:22Updated: 03/20/2026 22:23
Changes: 03/16/2026 10:22 (60), 03/20/2026 22:23 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.