VulnerabilityPublished 6 Feb 2026

CVE-2026-24920: Huawei HarmonyOS · Permissions, Privileges, and Access Controls

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.2Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% 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:N/I:H/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
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: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 6 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 =4.3.1 =4.3.0 =4.2.0	Fixed in–
HuaweiEMUI	Affected =15.0.0 =14.2.0	Fixed in–

AI-suggested

Monitor Huawei’s official channels for patches addressing CVE-2026-24920 and apply updates promptly once available.
Restrict physical and local access to HarmonyOS devices, especially in sensitive environments, to reduce the risk of local exploitation.
Implement strict access controls and endpoint security measures to detect and prevent unauthorized privilege escalations on devices running HarmonyOS.
Employ behavioral monitoring and anomaly detection focused on the AMS module to identify suspicious activity indicative of exploitation attempts.
Conduct regular security audits and penetration testing on HarmonyOS deployments to uncover potential exploitation vectors.
Educate staff on the risks of local device compromise and enforce policies limiting device usage to trusted personnel.
Where feasible, segment networks to isolate HarmonyOS devices from critical infrastructure to contain potential impacts.
Maintain comprehensive logging on HarmonyOS devices and integrate logs into centralized security information and event management (SIEM) systems for timely detection.

Description

Permission control vulnerability in the AMS module. Impact: Successful exploitation of this vulnerability may affect availability.

Impact

For European organizations, the primary impact of CVE-2026-24920 lies in the potential compromise of system integrity on Huawei HarmonyOS devices. This could lead to unauthorized modification of system or application states, potentially disrupting business operations or enabling further exploitation. While availability and confidentiality are not directly affected, integrity breaches can undermine trust in device behavior and data accuracy. Organizations relying on HarmonyOS for telecommunications infrastructure, IoT device management, or enterprise mobility may experience operational instability or increased risk of lateral movement by attackers. The local access requirement limits remote exploitation risks but raises concerns for insider threats or compromised endpoints within corporate networks. The absence of known exploits reduces immediate risk but does not preclude targeted attacks, especially in high-value sectors. Consequently, European entities using Huawei HarmonyOS devices should prioritize vulnerability management to maintain operational security and compliance with data protection regulations.

CWE-264Permissions, Privileges, and Access Controls (opens in a new tab)
CategoryOWASP Top 10 A01:2021: Broken Access Control (opens in a new tab)
Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.
MITRE does not allow mapping vulnerabilities to this entry; it groups weaknesses rather than naming one.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Feb 2026, 09:45 UTC

WeaknessesCWE-264

Technical details

References

Community reviews

Related threats