Cyber Resilience

CVE-2026-34852

DoS in Huawei Harmonyos 6.0.0

DoS
Published
13 April 2026
Modified
16 April 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H
EPSS Score 0.0016 5th percentile
Risk Priority 38 floored blend · peak EPSS

Summary

CVE-2026-34852 is a medium-severity Infinite Loop (CWE-835) vulnerability in Huawei Harmonyos. Its CVSS base score is 6.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 5th 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 SC-5 (Denial-of-service Protection) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Stack overflow vulnerability in the media platform. Impact: Successful exploitation of this vulnerability may affect availability.

CWE(s)
CWE-835

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
Why these techniques?

Stack overflow/infinite loop (CWE-835) directly enables application DoS via exploitation, matching T1499.004.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2024-57962Same product: Huawei Harmonyos
CVE-2024-56446Same product: Huawei Harmonyos
CVE-2026-24914Same product: Huawei Harmonyos
CVE-2026-34851Same product: Huawei Harmonyos
CVE-2025-66328Same product: Huawei Harmonyos
CVE-2026-34856Same product: Huawei Harmonyos
CVE-2024-54121Same product: Huawei Harmonyos
CVE-2024-56437Same product: Huawei Harmonyos
CVE-2024-57956Same product: Huawei Harmonyos
CVE-2026-24925Same product: Huawei Harmonyos

Affected Assets

huawei
harmonyos
6.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SC-5 Denial-of-service Protection
Detect
Catch it (NIST detect / respond)
  • SI-4 System Monitoring
Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match
prevent

Input validation directly blocks malformed media data that triggers the unreachable exit condition (CWE-835) leading to the stack overflow/DoS.

SC-5 Denial-of-service Protection good match
prevent

Denial-of-service protection mechanisms limit resource exhaustion caused by the infinite loop in the media platform.

SI-4 System Monitoring partial match
detect

Continuous monitoring of resource utilization and process behavior identifies the availability impact from the loop condition in real time.

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 (reviews, testing, static analysis) directly prevent introduction of infinite-loop defects.

ID.RA-01 partial match
prevents

Static analysis and vuln scanning during asset assessment can detect unreachable loop exits.

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
detects

Security testing can uncover infinite-loop conditions before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify loop-termination rules, indirectly reducing the weakness.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address loop termination and prevent infinite loops.

A.8.27 Secure system architecture and engineering principles none match
none

Secure architecture principles encourage designs that avoid unreachable exit conditions.

A.8.32 Change management none match
none

Change management can require review of loop logic when code is modified.

References