Export limit exceeded: 235489 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (21 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-0639 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2026-03-24 | 3.3 Low |
| in OpenHarmony v6.0 and prior versions allow a local attacker case DOS through missing release of memory. | ||||
| CVE-2025-12736 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2026-03-24 | 6.5 Medium |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker case sensitive information leak through use of uninitialized resource. | ||||
| CVE-2025-25277 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2026-03-24 | 6.3 Medium |
| in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through using incompatible type. This vulnerability can be exploited only in restricted scenarios. | ||||
| CVE-2025-41432 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2026-03-24 | 5.5 Medium |
| in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through out-of-bounds write. This vulnerability can be exploited only in restricted scenarios. | ||||
| CVE-2025-52458 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2026-03-24 | 5.5 Medium |
| in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through out-of-bounds write. This vulnerability can be exploited only in restricted scenarios. | ||||
| CVE-2025-26474 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2026-03-24 | 3.3 Low |
| 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. | ||||
| CVE-2025-6969 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2026-03-24 | 5 Medium |
| in OpenHarmony v5.1.0 and prior versions allow a local attacker cause DOS through improper input. | ||||
| CVE-2025-24298 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2025-08-12 | 8.4 High |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker arbitrary code execution in tcb through use after free. | ||||
| CVE-2025-24844 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2025-08-12 | 3.3 Low |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through missing release of memory. | ||||
| CVE-2025-24925 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2025-08-12 | 3.3 Low |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through missing release of memory. | ||||
| CVE-2025-25212 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2025-08-12 | 3.3 Low |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through improper input. | ||||
| CVE-2025-25278 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2025-08-12 | 8.4 High |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker arbitrary code execution in tcb through race condition. | ||||
| CVE-2025-26690 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2025-08-12 | 3.3 Low |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference. | ||||
| CVE-2025-27128 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2025-08-12 | 8.4 High |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker arbitrary code execution in tcb through use after free. | ||||
| CVE-2025-27536 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2025-08-12 | 3.3 Low |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through type confusion. | ||||
| CVE-2025-27562 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2025-08-12 | 3.3 Low |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through missing release of memory. | ||||
| CVE-2025-27577 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2025-08-12 | 8.4 High |
| in OpenHarmony v5.0.3 and prior versions allow a local attacker arbitrary code execution in tcb through race condition. | ||||
| CVE-2022-45877 | 1 Openharmony | 1 Openharmony | 2024-11-21 | 8.3 High |
| OpenHarmony-v3.1.4 and prior versions had an vulnerability. PIN code is transmitted to the peer device in plain text during cross-device authentication, which reduces the difficulty of man-in-the-middle attacks. | ||||
| CVE-2022-45118 | 1 Openharmony | 1 Openharmony | 2024-11-21 | 6.2 Medium |
| OpenHarmony-v3.1.2 and prior versions had a vulnerability that telephony in communication subsystem sends public events with personal data, but the permission is not set. Malicious apps could listen to public events and obtain information such as mobile numbers and SMS data without permissions. | ||||
| CVE-2022-44455 | 2 Openatom, Openharmony | 2 Openharmony, Openharmony | 2024-11-21 | 6.8 Medium |
| The appspawn and nwebspawn services within OpenHarmony-v3.1.2 and prior versions were found to be vulnerable to buffer overflow vulnerability due to insufficient input validation. An unprivileged malicious application would be able to gain code execution within any application installed on the device or cause application crash. | ||||