Huawei HarmonyOS
CVE-2025-58298
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-priv local app execution
-
DeliverySupply crafted package data to pkg mgmt module
-
ExploitOverflow stack buffer (CWE-121)
-
ExecutionCrash package management service
-
ImpactLocal denial of service
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires local access to a HarmonyOS 5.0.1 or 5.1.0 device with the ability to execute code at low privilege (PR:L), e.g. via an installed app, and the ability to feed crafted input to the package management module. Exploitation is limited by the local-only attack vector (no remote/network reach) and the low-privilege foothold prerequisite; impact is confined to availability (service crash/DoS) with no confidentiality or integrity effect, and no user interaction is needed once local access is obtained. |
| Impact | This is a genuinely moderate, availability-only issue rather than a top-tier priority. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base 5.5) is internally consistent: a local attacker with low privileges triggers a stack-based buffer overflow (CWE-121) in the HarmonyOS package management module, impacting only availability (C:N/I:N/A:H) - no confidentiality or integrity loss. All exploitation-likelihood signals point low: EPSS is 0.09% (0th percentile), there is no CISA KEV listing, and no public exploit code was identified. The local attack vector (AV:L) is the dominant risk-limiter - an attacker must already be able to run code or an app on the device, so this is a local DoS / crash primitive, not a remotely exploitable flaw. One caveat worth noting: the tags assert 'Buffer Overflow'/'Stack Overflow' (matching CWE-121), yet the vendor constrained impact strictly to availability; stack overflows can sometimes yield code execution, so the A:H-only scoping reflects Huawei's assessment and should be taken at face value absent further detail. The free-text description ('Data processing error') is vague and does not independently corroborate the stack-overflow mechanism - that comes from the CWE and tags. |
| Exploit ScenarioDerived | A malicious or compromised low-privilege app installed on a HarmonyOS 5.0.1 or 5.1.0 device supplies crafted package data to the package management module, overflowing a stack buffer and crashing or destabilizing the service. The result is a local denial of service against package-management functionality. No public proof-of-concept exploit has been identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
A stack-based buffer overflow in the HarmonyOS package management module allows locally-positioned code running at low privilege to feed crafted input into the component and crash or destabilize it, affecting Huawei HarmonyOS 5.0.1 and 5.1.0 devices. Impact is availability-only (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) - there is no confidentiality or integrity effect and no user interaction is required once the low-privilege foothold is obtained, for example through an installed app. No public exploit code has been identified at time of analysis, EPSS is 0.09% (0th percentile), and the CVE is not listed in CISA KEV; consistent with the independent assessment, this is a genuinely moderate, availability-only issue rather than a top-tier priority.
RemediationAI
Apply the fixed HarmonyOS release documented in Huawei's October 2025 consumer security bulletin at https://consumer.huawei.com/en/support/bulletin/2025/10/ ; that bulletin is the vendor's authoritative remediation source, and an exact fixed build number is not specified in the provided intelligence, so the version listed there should be treated as the patch version rather than one inferred from this report (patch status: available per vendor advisory). Users should apply available HarmonyOS system updates on 5.0.1 and 5.1.0 devices via Settings > System & updates. As compensating controls until the update is installed: restrict application installation to trusted, vendor-signed sources and review or remove low-privilege apps that interact with the package management module - the trade-off is reduced app flexibility and manual curation effort; audit for repeated package manager crashes or reboots, since exploitation manifests as availability loss rather than data compromise; and treat local low-privilege code execution (for example a malicious installed app) as the prerequisite to exploit, so hardening app-distribution and permission review reduces exposure. Note that no vendor patch workaround (such as disabling the package manager) is realistic on a shipping mobile OS, which makes timely platform updates the primary mitigation.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-121 (stack-based buffer overflow), reflected in the source tags 'Buffer Overflow' and 'Stack Overflow'. The vulnerable component is the HarmonyOS package management module, which handles install/update package metadata and is reported as suffering a data processing error when parsing malformed input - a stack-allocated buffer is written past its bounds, corrupting adjacent stack data and typically terminating the affected process (availability impact) rather than granting control of it. The CVSS v3.1 vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H and the independently assessed vector agree exactly: exploitation is confined to the local attack surface (AV:L) with no network reach, requires an attacker already executing at low privilege (PR:L), needs no user interaction (UI:N), stays within the same security scope (S:U), and produces only a high availability impact (A:H) with no C/I effect. Affected builds are identified via the CPE entries cpe:2.3:o:huawei:harmonyos:5.0.1:*:*:*:*:*:*:* and cpe:2.3:o:huawei:harmonyos:5.1.0:*:*:*:*:*:*:*, indicating operating-system-level firmware on the 5.0.1 and 5.1.0 branches. The practical exploit path is an installed local app that can exercise the package management interfaces with crafted package data; the local-only vector and the low-privilege prerequisite materially cap the practical risk.
Know when Harmonyos gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Local app-level trigger gives AV:L and PR:L with no user interaction; stack overflow is reliably reachable (AC:L); impact is availability-only per vendor, so C:N/I:N/A:H.
Primary rating from NVD.
CVSS VectorNVD
DescriptionNVD
Data processing error vulnerability in the package management module. Successful exploitation of this vulnerability may affect availability.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
Affected Products (CPE)NVD
Out-of-bounds heap write in Huawei HarmonyOS WEB module allows unauthenticated remote attackers to execute arbitrary cod
Permission verification vulnerability in the wpa_supplicant module Impact: Successful exploitation of this vulnerability
Permission management vulnerability in the PMS module. Rated critical severity (CVSS 9.8), this vulnerability is remotel
Vulnerability of access permissions not being strictly verified in the APPWidget module.Successful exploitation of this
Vulnerability of permissions not being strictly verified in the window management module.Successful exploitation of this
API permission management vulnerability in the Fwk-Display module.Successful exploitation of this vulnerability may caus
Vulnerability of defects introduced in the design process in the HiviewTunner module. Rated critical severity (CVSS 9.8)
The DP module has a service hijacking vulnerability.Successful exploitation of this vulnerability may affect some Super
Vulnerability of out-of-bounds parameter read/write in the Wi-Fi module. Rated critical severity (CVSS 9.8), this vulner
Vulnerability of commands from the modem being intercepted in the atcmdserver module. Rated critical severity (CVSS 9.8)
Some smartphones have configuration issues. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitab
Some smartphones have the out-of-bounds write vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is r
GitHub PoC
Exploit-DB