Cyber Resilience

CVE-2025-58291

Huawei Harmonyos 5.0.1 … 5.1.0

Published
11 October 2025
Modified
16 October 2025
Patch / advisory
View advisory
CVSS Score v3.1 3.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
EPSS Score 0.0010 1th percentile
Risk Priority 27 floored blend · peak EPSS

Summary

CVE-2025-58291 is a low-severity Path Traversal: '\..\filename' (CWE-29) 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

Vulnerability Data

Denial of service (DoS) vulnerability in the office service. Successful exploitation of this vulnerability may affect availability.

CWE(s)
CWE-29NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-58290Same product: Huawei Harmonyos
CVE-2024-57957Same product: Huawei Harmonyos
CVE-2025-53167Same product: Huawei Harmonyos
CVE-2025-31174Same product: Huawei Harmonyos
CVE-2023-39407Same product: Huawei Harmonyos
CVE-2026-28536Same product: Huawei Harmonyos
CVE-2025-58292Same product: Huawei Harmonyos
CVE-2025-54652Same product: Huawei Harmonyos
CVE-2025-54653Same product: Huawei Harmonyos
CVE-2025-54622Same product: Huawei Harmonyos

Affected Assets

huawei
harmonyos
5.0.1, 5.1.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly neutralizes the '\..\filename' sequence before pathname resolution occurs.

AC-3 Access Enforcement partial match

Access enforcement denies requests that resolve outside the intended directory even when the traversal sequence is present.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that block this traversal vector.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can discover path-traversal flaws but does not itself prevent them in production code.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate input validation and path canonicalization to block traversal sequences.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include directory sandboxing and safe file-access design that mitigate path traversal.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require neutralizing path traversal sequences such as '\..\filename'.

References