Cyber Resilience

CVE-2025-48905

Huawei Harmonyos 5.0.0

Published
06 June 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0026 17th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2025-48905 is a high-severity Inconsistency Between Implementation and Documented Design (CWE-1068) vulnerability in Huawei Harmonyos. Its CVSS base score is 8.1 (High).

Operationally, ranked at the 17th 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 SA-10 (Developer Configuration Management) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Wasm exception capture vulnerability in the arkweb v8 module Impact: Successful exploitation of this vulnerability may cause the failure to capture specific Wasm exception types.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-54120Same product: Huawei Harmonyos
CVE-2024-54110Same product: Huawei Harmonyos
CVE-2024-56436Same product: Huawei Harmonyos
CVE-2025-53183Same product: Huawei Harmonyos
CVE-2024-58045Same product: Huawei Harmonyos
CVE-2024-57955Same product: Huawei Harmonyos
CVE-2023-34157Same product: Huawei Harmonyos
CVE-2024-54107Same product: Huawei Harmonyos
CVE-2024-58112Same product: Huawei Harmonyos
CVE-2025-58280Same product: Huawei Harmonyos

Affected Assets

huawei
harmonyos
5.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V7.1.1

Mitigating Controls (NIST 800-53 r5) AI

Requires developer configuration management that tracks and controls changes to both design and code, reducing divergence between them.

Developer testing and evaluation activities directly examine whether the delivered implementation satisfies documented design and requirements.

Requires the developer to follow a documented development process that explicitly includes maintaining consistency between design artifacts and implementation.

Mandates use of an SDLC that incorporates security and privacy activities, thereby structuring development to keep implementation aligned with documented design.

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 include design-to-code verification activities that directly address implementation versus documented design mismatches.

ID.RA-07 partial match
prevents

Formal change and exception tracking reduces uncontrolled drift from documented designs but does not verify consistency.

PR.PS-01 partial match
prevents

Configuration management verifies deployed state against documented baselines, catching some but not all design-implementation drift.

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.

finds

Security testing can detect deviations, yet does not prevent the inconsistency from occurring.

prevents

Change management can catch drift after the fact, but does not guarantee initial implementation matches design.

degrades

Documented operating procedures help keep implementation aligned with stated design, but do not enforce design-level consistency.

prevents

Project-level design-to-implementation traceability directly reduces divergence between documented design and delivered code.

prevents

Secure SDLC mandates that implementation matches documented design artifacts, catching the inconsistency early.

prevents

Application security requirements can reference design, but do not themselves ensure implementation matches that design.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248873 The Trivial File Transfer Protocol (TFTP) server package must not be installed if not required for OL 8 operational support. prevents CWE-1068
RHEL 7 (2 rules)
  • V-204392 The Red Hat Enterprise Linux operating system must be configured so that the file permissions, ownership, and group membership of system files and commands match the vendor values. prevents CWE-1068
  • V-204621 The Red Hat Enterprise Linux operating system must not have the Trivial File Transfer Protocol (TFTP) server package installed if not required for operational support. prevents CWE-1068

References