CVE-2025-58286
Huawei Harmonyos 5.0.1 … 5.1.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:LSummary
CVE-2025-58286 is a low-severity Path Traversal: '/../filedir' (CWE-25) vulnerability in Huawei Harmonyos. Its CVSS base score is 3.3 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-33827
Vulnerability Data
Denial of service (DoS) vulnerability in the office service. Successful exploitation of this vulnerability may affect availability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly neutralizes path traversal sequences such as '/../' in externally supplied filenames before they are used to construct paths.
Access enforcement ensures that even a traversed path cannot grant unauthorized access to resources outside the intended directory.
Information flow enforcement can block unauthorized data flows that would result from a successful path traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and path sanitization that prevent traversal flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards require canonicalization and neutralization of '../' sequences in path construction.
Security testing in development catches path-traversal flaws before production deployment.
Secure development lifecycle mandates input validation and path sanitization that directly prevents traversal sequences.
Application security requirements explicitly call for controls against path traversal and directory escape attacks.
Secure architecture principles reduce exposure to path traversal through least-privilege file-system design.
Information access restriction limits which directories users or processes may traverse.