Skip to main content

Huawei HarmonyOS CVE-2026-41966

| EUVDEUVD-2026-30528 MEDIUM
Business Logic Errors (CWE-840)
2026-05-15 huawei GHSA-j276-f994-hf7m
5.6
CVSS 3.1 · Vendor: huawei
View

Attack ChainAIDerived

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

  1. Access
    Remote reconnaissance of smart sensing service API
  2. Delivery
    Craft permission-bypass request
  3. Exploit
    Trigger race condition or state-specific vulnerability
  4. Execution
    Bypass permission checks
  5. Persist
    Disclose sensor data or modify service state
  6. Impact
    Impact confidentiality or integrity

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V2 - Validation and Business Logic Business logic errors
Exploitation Conditions

Exploitation requires the smart sensing service to be network-accessible and operational on the target HarmonyOS device. The high attack complexity (AC:H) indicates the attacker must satisfy specific preconditions not clearly detailed in the provided description: these may include triggering a race condition in the service's permission validation logic, exploiting a non-default service configuration, or leveraging a specific sequence of API calls. No explicit requirement for authentication (PR:N) or user interaction (UI:N) is stated. Exploitation is limited to partial information disclosure and integrity impacts (C:L/I:L) - full system takeover or denial of service is not achieved. Devices with the smart sensing service disabled or network-isolated are not affected.

Impact

CVSS 5.6 with AV:N/AC:H/PR:N indicates moderate real-world risk with meaningful exploitation barriers. The high attack complexity mitigates the severity despite the unauthenticated network vector - an attacker must overcome specific preconditions such as race conditions, non-default service configurations, or precise timing windows. EPSS data not provided, limiting exploitation probability assessment. The 'Information Disclosure' tag and partial confidentiality/integrity impact (C:L/I:L) suggest this is a privacy or data leakage issue rather than a critical system breach vector. No KEV listing or POC availability reduces immediate operational priority, but organizations deploying HarmonyOS devices in sensitive environments (smart home, healthcare, IoT) should prioritize assessment. The unspecified version range in CPE (harmonyos:*) indicates broad affected population; patch availability and specific vulnerable versions are unknown from provided data, creating assessment uncertainty.

Exploit ScenarioDerived

A remote attacker crafts a malformed or specially-timed request to the HarmonyOS smart sensing service, exploiting inadequate permission checks to bypass access control logic. Under non-default or race-condition circumstances, the attacker gains unauthorized read access to sensor data (e.g., accelerometer, gyroscope, location-derived information) or temporarily disrupts the service's availability, potentially inferring user activity or device state without proper authorization.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.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 – May 15, 2026

Permission control vulnerability in Huawei HarmonyOS smart sensing service allows remote attackers to bypass access controls and disclose sensitive information with moderate complexity. The vulnerability affects service confidentiality and integrity across HarmonyOS versions, with CVSS 5.6 (AV:N/AC:H/PR:N/UI:N) indicating network-accessible exploitation requiring non-trivial conditions. No active exploitation in CISA KEV or public exploit code identified at time of analysis.

RemediationAI

Consult Huawei's official security bulletin at https://consumer.huawei.com/en/support/bulletin/2026/5/ for patch availability and exact fix versions specific to your HarmonyOS device model and build. If vendor-released patches are available, apply them immediately to the smart sensing service component. If patching is not yet available or delays are expected, implement compensating controls: disable or restrict network access to the smart sensing service via firewall rules or SELinux/AppArmor policies, disable sensor APIs for untrusted remote callers, enforce strict input validation on service requests, and monitor smart sensing service logs for anomalous permission requests. Note that disabling sensing features may impact legitimate smart home automation or health-tracking functionality - validate impacts on user workflows before deployment.

Affected VersionsENISA

HarmonyOS 6.0.0
HarmonyOS 6.1.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 resides in HarmonyOS's smart sensing service, a permission-sensitive component responsible for managing access to device sensor data and system capabilities. CWE-840 (Use of Inadequately Specified Permissions) indicates the root cause is insufficient or improperly enforced permission checks within the service's request validation logic. The network attack vector (AV:N) suggests the service accepts remote requests, likely via inter-process communication (IPC) or network APIs, while the high attack complexity (AC:H) implies exploitation requires overcoming non-default configurations, timing conditions, or specific service states. The partial scope unchanged (S:U) and limited impact (C:L, I:L, A:L) suggest the vulnerability grants access to a narrow subset of sensor data or temporary disruption rather than full system compromise.

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

No credit card · 7-day full trial

Severity by source

Vendor (huawei) PRIMARY 5.6 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Primary rating from Vendor (huawei) · only source for this CVE.

CVSS VectorVendor: huawei

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

DescriptionCVE.org

Permission control vulnerability in the smart sensing service. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Data Quality
5 sources
Confidence: Medium

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

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

CVE-2026-34865 CRITICAL
10.0 Apr 13

Out-of-bounds heap write in Huawei HarmonyOS WEB module allows unauthenticated remote attackers to execute arbitrary cod

CVE-2024-32991 CRITICAL
9.8 May 14

Permission verification vulnerability in the wpa_supplicant module Impact: Successful exploitation of this vulnerability

CVE-2023-46773 CRITICAL
9.8 Dec 06

Permission management vulnerability in the PMS module. Rated critical severity (CVSS 9.8), this vulnerability is remotel

CVE-2023-44116 CRITICAL
9.8 Oct 11

Vulnerability of access permissions not being strictly verified in the APPWidget module.Successful exploitation of this

CVE-2023-44105 CRITICAL
9.8 Oct 11

Vulnerability of permissions not being strictly verified in the window management module.Successful exploitation of this

CVE-2023-44106 CRITICAL
9.8 Oct 11

API permission management vulnerability in the Fwk-Display module.Successful exploitation of this vulnerability may caus

CVE-2023-41297 CRITICAL
9.8 Sep 25

Vulnerability of defects introduced in the design process in the HiviewTunner module. Rated critical severity (CVSS 9.8)

CVE-2023-41294 CRITICAL
9.8 Sep 25

The DP module has a service hijacking vulnerability.Successful exploitation of this vulnerability may affect some Super

CVE-2023-39405 CRITICAL
9.8 Aug 13

Vulnerability of out-of-bounds parameter read/write in the Wi-Fi module. Rated critical severity (CVSS 9.8), this vulner

CVE-2023-37242 CRITICAL
9.8 Jul 06

Vulnerability of commands from the modem being intercepted in the atcmdserver module. Rated critical severity (CVSS 9.8)

CVE-2022-46327 CRITICAL
9.8 Dec 20

Some smartphones have configuration issues. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitab

CVE-2022-46326 CRITICAL
9.8 Dec 20

Some smartphones have the out-of-bounds write vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is r

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy