LearnCTEM.com, Best CTEM Learning Platform
CVE Intelligence Hub

CVE-2026-34856: Huawei Harmonyos Race Condition (CVSS 7.3)

CVE-2026-34856 is a high severity race condition in Huawei Harmonyos with a CVSS score of 7.3. Apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Last updated: Jun 17, 2026

Quick answer

Direct answer

CVE-2026-34856 is a high severity race condition in Huawei Harmonyos with a CVSS score of 7.3. Apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Risk scores

CVSS base score
7.3HIGH
EPSS probability
0.16%
Higher than 4 percent of all CVEs
CISA KEV
Not listed
CVSS metricWhat it means
Attack vector (AV:L)Local access needed
Attack complexity (AC:L)Low complexity
Privileges required (PR:N)No privileges required
User interaction (UI:N)No user interaction
Scope (S:U)Scope unchanged
Confidentiality (C:L)Low confidentiality impact
Integrity (I:L)Low integrity impact
Availability (A:H)High availability impact

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

About Huawei Harmonyos

CVE-2026-34856 affects Huawei Harmonyos, a product from Huawei. Before acting, confirm where Huawei Harmonyos runs in your estate, who owns it and whether it is reachable from the internet, because exposure decides real risk more than the score alone.

What the flaw is

In plain terms: UAF vulnerability in the communication module. Impact: Successful exploitation of this vulnerability may affect availability.

The weakness class is Race Condition. Two operations collide in timing, breaking a security assumption.

Based on its CVSS vector, the flaw needs local or adjacent access, needs no login, and needs no user interaction. Apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Affected versions and timeline

FieldDetail
ProductHuawei Harmonyos
Affected versionsHarmonyos 6.0.0
PublishedApr 13, 2026
Last modifiedJun 17, 2026
Added to CISA KEVNot listed
Assigning CNApsirt@huawei.com

How to detect it

  • Inventory every instance of Huawei Harmonyos and record the running version against the affected range above.
  • Check external attack surface scans for internet facing instances of the component.
  • Review logs on affected systems for unusual requests, errors or new processes around the vulnerable function.
  • Confirm with an authenticated vulnerability scan once your scanner has a check for this CVE.

How to fix it

  • Apply the fixed version of Huawei Harmonyos named in the vendor advisory.
  • If patching must wait, restrict network access to the affected service and put it behind authentication or a web application firewall rule.
  • Rescan after the change to prove the exposure is gone, then close the ticket.

CTEM action plan

CTEM stageWhat to do for this CVE
ScopeAdd every business service that depends on Huawei Harmonyos to the current CTEM cycle.
DiscoverFind all instances, including shadow and cloud deployments, and record versions and exposure.
PrioritizeRank using EPSS and CVSS together with asset exposure and business impact.
ValidateConfirm the flaw is reachable and exploitable in your environment and that compensating controls work.
MobilizeAssign the fix to the asset owner with a due date matched to the priority, then verify closure.

CWE References

Technical References

Frequently asked questions

CVE-2026-34856 is a high severity race condition in Huawei Harmonyos with a CVSS score of 7.3. Apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Related CVEs

CRITICAL10.0
CVE-2026-34865
Huawei Harmonyos

Out-of-bounds write vulnerability in the WEB module.Impact: Successful exploitation of this vulnerability will affect availability and confidentiality.

Apr 13, 2026
HIGH7.7
CVE-2026-34853
Huawei Harmonyos

Permission bypass vulnerability in the LBS module. Impact: Successful exploitation of this vulnerability may affect availability.

Apr 13, 2026
CRITICAL9.6
CVE-2026-28536
Huawei Harmonyos

Authentication bypass vulnerability in the device authentication module. Impact: Successful exploitation of this vulnerability will affect integrity and confidentiality.

Mar 5, 2026
CRITICAL10.0
CVE-2026-0068
Google Android

In createSessionInternal of PackageInstallerService.java, there is a possible method to remove a DPC app from a managed device without DO consent due to desync from persistence. This could lead to local escalation of privilege if a user can install a malicious app with no additional execution privileges needed. User interaction is needed for exploitation.

Jun 17, 2026
CRITICAL10.0
CVE-2026-0083
Google Android

In Nfc::eventCallback() of Nfc.h, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Jun 17, 2026
CRITICAL9.8
CVE-2026-56188
Microsoft Windows 10 1607

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Server Network driver allows an unauthorized attacker to execute code over a network.

Jul 14, 2026
All Huawei CVEs in 2026
Your next credential

Earn your free CTEM certification.

Learn to scope, prioritize, validate and mobilize fixes for CVEs like CVE-2026-34856 with a free CTEM certification.

Free to takePublicly verifiable

Beginner / Practitioner / Program Leader

Explore certifications