VulnerabilityPublished 6 Feb 2026Updated 5 Mar 2026

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

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.1Medium

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:L/UI:N/S:U/C:H/I:N/A:L

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

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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 =6.0.0	Fixed in–

AI-suggested

To mitigate CVE-2026-24924, organizations should implement the following specific measures: 1) Restrict physical and local access to devices running HarmonyOS 6.0.0 to trusted personnel only, minimizing opportunities for local exploitation. 2) Enforce strict user privilege management and regularly audit user accounts to ensure minimal necessary permissions are granted, reducing the risk of low-privilege exploitation. 3) Monitor and log access to the print module and related services to detect unusual or unauthorized activities early. 4) Apply device hardening practices such as disabling unnecessary services and modules that could be leveraged in exploitation. 5) Stay informed on Huawei's security advisories for the release of patches or updates addressing this vulnerability and prioritize timely deployment once available. 6) Consider network segmentation and endpoint security controls to limit lateral movement if a device is compromised. 7) Educate users about the risks of local device access and enforce policies to prevent unauthorized physical access. These targeted actions go beyond generic advice by focusing on controlling local access, privilege management, and proactive monitoring specific to the print module context.

Description

Vulnerability of improper permission control in the print module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

Impact

The primary impact of CVE-2026-24924 is the potential unauthorized disclosure of confidential information managed by the print module in HarmonyOS 6.0.0. Organizations relying on Huawei devices running this OS version could face data confidentiality breaches if an attacker gains local access with low privileges. Although the vulnerability does not compromise system integrity or availability, the exposure of sensitive data could lead to privacy violations, intellectual property theft, or leakage of sensitive operational information. This is particularly critical for enterprises and government entities using Huawei devices in sensitive environments. The requirement for local access and low privileges somewhat limits the attack surface but does not eliminate risk, especially in scenarios where devices are shared, lost, or physically accessed by malicious insiders. The absence of known exploits reduces immediate risk but also means organizations should proactively address the vulnerability before exploitation occurs. Overall, the impact is significant in confidentiality terms but limited in scope due to the local attack vector and privilege requirements.

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

consumer.huawei.com/en/support/bulletin/2026/3/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

WeaknessesCWE-264

Technical details

References

Community reviews

Related threats