CVE-2025-64315VulnerabilityPublished 28 Nov 2025

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

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 4.4 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.4Medium

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

EPSS: 0.08% 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:R/S:U/C:L/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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	Fixed in–

AI-suggested

1. Monitor Huawei's official security advisories closely and apply patches or updates for HarmonyOS 5.1.0 as soon as they become available to address this vulnerability. 2. Restrict physical and local access to Huawei devices within organizational environments to trusted personnel only. 3. Educate users about the risks of interacting with untrusted applications or prompts that could trigger exploitation of local vulnerabilities. 4. Implement mobile device management (MDM) solutions to enforce strict app installation policies and permissions on HarmonyOS devices. 5. Conduct regular audits of file management permissions and access controls on affected devices to detect misconfigurations or anomalies. 6. Where possible, isolate sensitive applications or data using containerization or sandboxing techniques to limit the impact of potential exploits. 7. Encourage users to report suspicious behavior promptly and maintain incident response readiness for potential local compromise scenarios.

Description

CVE-2025-64315 is a medium-severity configuration defect vulnerability in Huawei HarmonyOS version 5.1.0's file management module. It involves improper permissions, privileges, and access controls (CWE-264) that could allow an attacker with local access and user interaction to compromise app data confidentiality and integrity. The vulnerability does not require privileges and has low complexity to exploit but requires user interaction. There are no known exploits in the wild yet. The impact is limited to confidentiality and integrity without affecting availability. European organizations using HarmonyOS devices could be affected, especially where Huawei devices have significant market penetration. Mitigation involves applying patches once available, restricting local access, and monitoring file management operations closely. Countries with higher Huawei device usage and strategic interest in Huawei technology, such as Germany, France, Italy, Spain, and the UK, are more likely to be impacted.

Impact

For European organizations, the impact of CVE-2025-64315 primarily concerns confidentiality and integrity of application data on Huawei HarmonyOS devices. Organizations relying on Huawei smartphones, tablets, or IoT devices running version 5.1.0 could face risks of data leakage or unauthorized data modification if attackers gain local access and trick users into interaction. This could affect sensitive corporate or personal information stored within apps, potentially leading to data breaches or manipulation of critical app data. Although availability is not impacted, the breach of confidentiality and integrity can undermine trust and compliance with data protection regulations such as GDPR. The risk is heightened in sectors with high Huawei device adoption or where employees use such devices for work purposes. Since exploitation requires local access and user interaction, remote attacks are less likely, but insider threats or physical device access scenarios remain relevant. The absence of known exploits reduces immediate risk but does not eliminate future exploitation potential.

Summary

CVE-2025-64315 is a vulnerability identified in Huawei's HarmonyOS version 5.1.0, specifically within the file management module. The root cause is a configuration defect related to permissions, privileges, and access controls (classified under CWE-264). This defect allows unauthorized or insufficiently authorized access to app data, potentially compromising its confidentiality and integrity. The vulnerability requires local access (AV:L), has low attack complexity (AC:L), does not require privileges (PR:N), but does require user interaction (UI:R). The scope remains unchanged (S:U), meaning the impact is confined to the vulnerable component without affecting other system components. The CVSS v3.1 base score is 4.4, indicating a medium severity level. Exploitation could allow an attacker to read or modify app data improperly, but it does not affect system availability. No known exploits have been reported in the wild, and no patches are currently linked, suggesting that mitigation is pending. The vulnerability highlights the importance of correct permission configurations in OS modules managing sensitive data. Given Huawei's market presence in mobile and IoT devices running HarmonyOS, this vulnerability could be leveraged in targeted attacks where local access is feasible, such as through malicious apps or social engineering to induce user interaction.

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/cn/support/bulletinlaptops/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:29 UTC

WeaknessesCWE-264

Technical details

References

Community reviews

Related threats