CVE-2025-58312VulnerabilityPublished 28 Nov 2025

CVE-2025-58312: Huawei HarmonyOS · Permissions, Privileges, and Access Controls

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.1Medium

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

EPSS: 0.07% 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:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: High
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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 28 Nov 2025
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 2026-10-25.

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 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
Huawei HarmonyOS	Affected =5.1.0 =5.0.1 =6.0.0	Fixed in–

AI-suggested

1. Restrict physical and local network access to Huawei devices running affected HarmonyOS versions to trusted personnel only. 2. Implement strict access controls and monitoring on devices to detect unusual App Lock behavior or permission escalations. 3. Employ endpoint detection and response (EDR) solutions capable of identifying anomalous local privilege abuse or denial of service attempts. 4. Isolate critical Huawei devices on segmented networks to limit lateral movement in case of compromise. 5. Educate users about the risks of local exploitation and enforce policies against unauthorized device access. 6. Monitor Huawei's security advisories closely and apply patches or firmware updates immediately upon release. 7. Consider deploying alternative security controls or device management solutions that can override or supplement App Lock protections. 8. Conduct regular security audits and penetration testing focusing on permission enforcement mechanisms within HarmonyOS environments. 9. Maintain incident response readiness to quickly address any exploitation attempts. 10. Collaborate with Huawei support channels for guidance on interim mitigations or workarounds.

Description

CVE-2025-58312 is a medium severity permission control vulnerability in Huawei HarmonyOS's App Lock module affecting versions 5.0.1, 5.1.0, and 6.0.0. The flaw relates to improper permissions, potentially impacting system availability if exploited. Exploitation requires local access with high attack complexity and no user interaction, and no privileges or authentication are needed. Although the CVSS vector indicates a confidentiality impact, the description emphasizes availability impact, suggesting some ambiguity in impact assessment.

Impact

For European organizations, the primary impact of CVE-2025-58312 lies in potential availability disruptions on devices running affected HarmonyOS versions. This could translate into denial of service conditions on Huawei smartphones, tablets, or IoT devices used within corporate environments, potentially affecting business continuity. Confidentiality impact indicated by the CVSS vector suggests possible unauthorized access to sensitive data, which could lead to data breaches if exploited. The requirement for local access limits remote exploitation risks but raises concerns for insider threats or scenarios where attackers gain physical or local network access. Organizations relying on Huawei devices for critical communications or operations may experience interruptions or degraded service. Additionally, the vulnerability could be leveraged in targeted attacks against high-value assets, especially in sectors like telecommunications, manufacturing, or government agencies where Huawei devices are prevalent. The absence of patches increases exposure duration, necessitating proactive risk management. Overall, the vulnerability could undermine trust in device security and complicate compliance with European data protection regulations if confidentiality or availability is compromised.

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/2025/11/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Dec 2025, 04:32 UTC

WeaknessesCWE-264

Technical details

References

Community reviews

Related threats