CVE-2025-58314VulnerabilityPublished 28 Nov 2025

CVE-2025-58314: Huawei HarmonyOS · Out-of-bounds Read

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 6.6 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.6Medium

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
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: 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: 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 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 =4.3.1 =4.3.0 =4.2.0 =4.0.0 =3.1.0 =3.0.0 =2.0.0	Fixed in–

AI-suggested

1. Implement strict local access controls and user privilege management on devices running HarmonyOS to limit opportunities for exploitation. 2. Monitor system logs and behavior for anomalous local memory access patterns or crashes related to driver modules. 3. Enforce network segmentation to isolate Huawei HarmonyOS devices, reducing risk from compromised local accounts spreading laterally. 4. Prepare incident response plans specifically addressing potential memory corruption or data leakage scenarios on affected devices. 5. Engage with Huawei support channels to obtain timely security updates or patches once they become available. 6. Conduct regular security audits and vulnerability scans on HarmonyOS devices to detect unpatched vulnerabilities. 7. Educate users and administrators about the risks of local privilege misuse and encourage strong authentication mechanisms. 8. Where possible, limit installation of untrusted applications or drivers that could exploit the vulnerability. 9. Consider deploying endpoint detection and response (EDR) tools capable of identifying exploitation attempts targeting memory vulnerabilities. 10. Maintain up-to-date backups of critical data and configurations to enable recovery in case of availability impact.

Description

CVE-2025-58314 is an out-of-bounds read vulnerability (CWE-125) in Huawei HarmonyOS affecting multiple versions from 2.0.0 to 6.0.0. It arises from improper memory access in a component driver module, potentially leading to unauthorized disclosure of sensitive information and partial disruption of system availability. The vulnerability requires local access with low privileges and no user interaction, with an attack vector classified as local. The CVSS 3.1 base score is 6.6 (medium severity), reflecting high confidentiality impact, low integrity impact, and low availability impact.

Impact

For European organizations, the primary impact of CVE-2025-58314 lies in potential confidentiality breaches and partial availability disruptions of devices running HarmonyOS. This is particularly critical for sectors relying on Huawei hardware and software, such as telecommunications providers, IoT device manufacturers, and enterprises using Huawei smartphones or embedded systems. Confidentiality impact could lead to leakage of sensitive corporate or personal data, undermining privacy and compliance with regulations like GDPR. Availability impact, though rated low, could disrupt critical services or device functionality, affecting operational continuity. Given the local attack vector and low privilege requirement, insider threats or attackers with limited access could exploit this vulnerability, increasing risk in environments with shared device usage or insufficient access controls. The absence of known exploits reduces immediate risk but also means organizations must proactively prepare defenses. The vulnerability could also be leveraged as part of a multi-stage attack chain, escalating impact beyond the initial local scope. Overall, European organizations with Huawei HarmonyOS deployments face moderate risk that warrants attention due to potential data exposure and service degradation.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

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-125

Technical details

References

Community reviews

Related threats