What is the CVSS score of CVE-2026-34851?

CVE-2026-34851 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.0%.

Harmonyos CVE-2026-34851

EUVD-2026-21794 HIGH

Race Condition (CWE-362)

2026-04-13 huawei

Information Disclosure Race Condition Harmonyos Huawei

7.5

CVSS 3.1 · NVD

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Local access as authenticated user
Delivery

Trigger event notification processing
Exploit

Manipulate timing of concurrent operations
Execution

Exploit race condition in module
Impact

Cause temporary availability disruption

Vulnerability Assessment

Weakness	CWE CWE-362 OWASP Top 10:2025 A06:2025 - Insecure Design ASVS 5.0 V15 - Secure Coding and Architecture Concurrency control, locking MITRE ATT&CK 1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Impact	This vulnerability presents minimal practical risk despite its race condition classification. The CVSS vector AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L establishes multiple attack barriers: local-only access requirement, high attack complexity, requirement for authenticated user privileges, mandatory user interaction, and impact limited to availability (no confidentiality or integrity impact). The CVSS score of 2.2 (low severity) reflects these constraints. The exploitation requires precise timing coordination by a low-privileged user while triggering user interaction, making practical exploitation difficult. No evidence of public exploit code or active exploitation (KEV status not indicated) further reduces real-world concern. This is a textbook example of a theoretically valid but practically low-impact vulnerability; organizations should prioritize patching only after addressing higher-severity issues.
Exploit ScenarioDerived	A local, low-privileged user on a HarmonyOS device must trigger a specific sequence of user interactions that causes the event notification module to process concurrent operations during a narrow synchronization window. By carefully timing their actions, they could disrupt notification processing and cause a temporary denial of service. However, the requirement for user interaction and high attack complexity makes this scenario unlikely in practice.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 13, 2026

Race condition in Huawei HarmonyOS event notification module allows local authenticated users with user interaction to cause denial of service through availability impact. The vulnerability requires local access, high attack complexity, and user interaction; with a CVSS score of 2.2, it represents minimal real-world risk. No public exploit code or active exploitation has been confirmed at this time.

RemediationAI

Users should consult Huawei's official security bulletins at https://consumer.huawei.com/en/support/bulletin/2026/4/ (consumer devices) and https://consumer.huawei.com/en/support/bulletinlaptops/2026/4/ (laptops) for specific patched HarmonyOS versions and deployment instructions. Apply the recommended security update when available from Huawei. Given the low CVSS score (2.2) and high attack complexity, patching can be scheduled as part of routine maintenance rather than emergency response. No workarounds are documented; patching is the primary remediation path.

Affected VersionsENISA

HarmonyOS 6.0.0

HarmonyOS 5.1.0

Affected Packages

euvd harmonyos no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability exists in HarmonyOS's event notification module and is classified as a race condition (CWE-362), a timing-dependent flaw where improper synchronization between concurrent operations allows an attacker to manipulate state during a narrow window. The affected product is Huawei HarmonyOS across multiple versions (cpe:2.3:a:huawei:harmonyos:*:*:*:*:*:*:*:*), indicating the flaw is present in a range of releases. Race conditions in event handling systems typically arise from unsynchronized access to shared resources during notification processing, which can result in logic errors or resource exhaustion when exploited by manipulating timing of concurrent operations.

Know when Harmonyos gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Severity Changed

Oct 26, 2026 - 21:23 NVD

LOW HIGH

CVSS changed

Oct 26, 2026 - 21:23 NVD

2.2 (LOW) 7.5 (HIGH)

CVE Published

Apr 13, 2026 - 03:44 nvd

LOW 2.2

DescriptionNVD

Race condition vulnerability in the event notification module. Impact: Successful exploitation of this vulnerability may affect availability.

Threat Intelligence Overview

EPSS Score

0.0%

Top 100% exploitable

Data Quality

5 sources

Confidence: Medium

EUVD

NVD

CVE.org

EPSS

Vulnrichment

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Defer

Exploitation

None

System Exposure· derived

Open

Automatable

Human Impact· derived

Low

Technical Impact

Partial

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Race Condition MEDIUM

Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).