Security readout for executives and security teams
Plain-English summary
CVE-2026-28549 is a Huawei HarmonyOS permission-management race condition. A local, low-privileged attacker could potentially disrupt device availability, with limited confidentiality and integrity impact. The main business concern is device reliability for affected HarmonyOS 6.0.0 and 5.1.0 deployments.
Executive priority
Treat as a moderate-priority endpoint reliability issue. It is not described as remotely exploitable or actively exploited, but affected HarmonyOS fleets should be identified and updated through Huawei guidance.
Technical view
The CVE describes CWE-362 in HarmonyOS permission management. CVSS 3.1 is 6.6: local attack vector, low complexity, low privileges, no user interaction, unchanged scope, low confidentiality/integrity impact, and high availability impact.
Likely exposure
Exposure appears limited to devices running Huawei HarmonyOS 6.0.0 or 5.1.0. The attack vector is local and requires low privileges, so remote internet exposure is not indicated by the CVE data.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not listed as KEV. Public details are sparse and do not describe exploit mechanics beyond a race condition affecting availability.
Researcher notes
The public record does not provide vulnerable code paths, fixed build numbers, or proof-of-concept details. Analysis should focus on permission-service race behavior, local privilege context, and availability impact without assuming remote reachability.
Mitigation direction
- Review Huawei March 2026 security bulletins for affected device models and update guidance.
- Prioritize updates for managed devices running HarmonyOS 6.0.0 or 5.1.0.
- Restrict unnecessary local user access on shared or high-value devices.
- Monitor Huawei support channels for revised advisories or additional remediation details.
Validation and detection
- Inventory HarmonyOS devices and record exact OS versions.
- Compare devices against Huawei March 2026 bulletin applicability.
- Confirm remediation status through enterprise device management or local system update records.
- Track availability incidents on affected devices until remediation is complete.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-28549 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H1.84.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.6MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://consumer.huawei.com/en/support/bulletin/2026/3/CVE reference
- https://consumer.huawei.com/en/support/bulletinlaptops/2026/3/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.