VulnerabilityPublished 5 Mar 2026

CVE-2026-28539: Huawei HarmonyOS · Data Processing Errors

Affects Huawei HarmonyOSSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.2 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.05% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
HuaweiHarmonyOS	Affected =6.0.0 =5.1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-28539, organizations should implement strict access controls to limit local access to devices running affected HarmonyOS versions. Physical security measures should be enhanced to prevent unauthorized device access. Monitoring and restricting installation of untrusted applications can reduce the risk of local malware exploiting the vulnerability. Huawei should be engaged to provide timely patches; once available, these should be applied promptly. Until patches are released, consider isolating affected devices from sensitive networks or data. Employ certificate lifecycle management best practices, including regular certificate rotation and revocation, to minimize exposure if certificate data is compromised. Security teams should audit and monitor certificate management module logs for unusual activity. Additionally, educating users about the risks of local device access and enforcing device encryption can help protect sensitive data. Organizations should also prepare incident response plans for potential confidentiality breaches related to certificate data.

Description

Data processing vulnerability in the certificate management module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

Impact

The primary impact of CVE-2026-28539 is the compromise of confidentiality related to certificate management in Huawei HarmonyOS devices. Successful exploitation could allow attackers to access sensitive certificate data, which may facilitate further attacks such as man-in-the-middle, impersonation, or unauthorized access to encrypted communications. Although the vulnerability does not affect integrity or availability, the breach of confidentiality can undermine trust in secure communications and authentication processes. The requirement for local access limits the attack surface, reducing the risk of widespread remote exploitation. However, in environments where devices are shared, physically accessible, or targeted by local malware, the risk increases. Organizations relying on HarmonyOS for critical infrastructure, secure communications, or sensitive data processing could face increased exposure to data leakage or espionage. The absence of known exploits currently reduces immediate risk but does not preclude future exploitation. The medium severity rating reflects the balance between the potential impact on confidentiality and the limited attack vector.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Mar 2026, 08:33 UTC

WeaknessesCWE-19

Technical details

References

Community reviews

Related threats