CVE-2026-28544
CVE-2026-28544 is a medium-severity vulnerability in Huawei Harmonyos with a CVSS 3.x base score of 6.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.
Key facts
- Severity: Medium (CVSS 3.x base score 6.2)
- EPSS exploit prediction: 0% (1st percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2026-9804
- Weakness: CWE-362
- Affected product: Huawei Harmonyos
- Published:
- Last modified:
Description
Race condition vulnerability in the printing module. Impact: Successful exploitation of this vulnerability may affect availability.
Frequently asked questions
- What is CVE-2026-28544?
- Race condition vulnerability in the printing module. Impact: Successful exploitation of this vulnerability may affect availability.
- How severe is CVE-2026-28544?
- CVE-2026-28544 has a CVSS 3.x base score of 6.2, rated medium severity. It is exploitable over local access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity high, and availability low.
- Is CVE-2026-28544 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-28544?
- CVE-2026-28544 affects Huawei Harmonyos. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-28544?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2026-28544 have an EU (EUVD) identifier?
- Yes. CVE-2026-28544 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-9804.
- When was CVE-2026-28544 published?
- CVE-2026-28544 was published on 2026-03-05 and last updated on 2026-06-17.
References
- https://consumer.huawei.com/en/support/bulletin/2026/3/
- https://consumer.huawei.com/en/support/bulletinlaptops/2026/3/
Affected products (1)
- cpe:2.3:o:huawei:harmonyos:6.0.0:*:*:*:*:*:*:*
More vulnerabilities in Huawei Harmonyos
- CVE-2023-34157 — Critical (CVSS 10.0): Vulnerability of HwWatchHealth being hijacked.Successful exploitation of this vulnerability may cause repeated pop-up…
- CVE-2023-52381 — Critical (CVSS 9.8): Script injection vulnerability in the email module.Successful exploitation of this vulnerability may affect service…
- CVE-2023-52378 — Critical (CVSS 9.8): Vulnerability of incorrect service logic in the WindowManagerServices module.Successful exploitation of this…
- CVE-2023-52370 — Critical (CVSS 9.8): Stack overflow vulnerability in the network acceleration module.Successful exploitation of this vulnerability may cause…
- CVE-2023-52103 — Critical (CVSS 9.8): Buffer overflow vulnerability in the FLP module. Successful exploitation of this vulnerability may cause out-of-bounds…
- CVE-2023-46773 — Critical (CVSS 9.8): Permission management vulnerability in the PMS module. Successful exploitation of this vulnerability may cause…
All CVEs affecting Huawei Harmonyos →
Other CWE-362 (Race Condition) vulnerabilities
- CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
- CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
- CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
- CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
- CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
- CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…