Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRun unprivileged code/app on HarmonyOS device
-
ExploitRepeatedly invoke location service module
-
ExecutionWin race-condition timing window
-
ImpactDisrupt location service availability
Vulnerability Assessment
| Weakness |
CWE
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. |
| Exploitation Conditions | Exploitation requires local access to the HarmonyOS device (AV:L) - most plausibly an attacker-controlled unprivileged process or installed app interacting with the location service module; it is not remotely reachable per the supplied vector. The flaw is a race condition (CWE-362) in the location service, so a successful trigger depends on winning a timing window, though the exact trigger is not described in the available sources. Limiting factors that reduce realistic risk: no network vector, impact is low and the authoritative impact text limits it to availability (temporary service disruption rather than full compromise), and specific affected/fixed versions are not enumerated in the provided data. Affected product per CPE is Huawei HarmonyOS across its consumer device bulletins (phones, wearables, laptops). |
| Impact | This is a moderate-severity issue (CVSS 5.9) whose real-world risk is meaningfully constrained by its local attack vector. The CVSS vector (AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) shows local access with no required privileges and no user interaction, but low impact across all three dimensions - meaning no single catastrophic outcome. There is no EPSS score, no CISA KEV listing, and no public PoC in the provided data, so exploitation is not confirmed and no automatable mass-exploitation signal exists; the vuln.today decision label 'this_month' aligns with a non-emergency, scheduled-patching priority rather than a drop-everything response. Two conflicts should be flagged for the defender: (1) the stated Impact text says the flaw 'may affect availability' only, yet the supplied CVSS vector asserts C:L and I:L as well, and the tag set includes 'Information Disclosure' - so the confidentiality/integrity impact is asserted by metadata but not corroborated by the human-readable impact statement; and (2) CWE-362 and the 'Race Condition' tag imply a timing-dependent trigger whose reliability (and therefore practical exploitability) is not described in the sources. Net: a genuine but low-urgency local flaw, not a high-CVSS-but-overstated-risk item and not a widespread-exploitation emergency. |
| Exploit ScenarioDerived | A local attacker with code execution on a HarmonyOS device (for example via an installed unprivileged app) repeatedly interacts with the location service module to win a race-condition timing window, driving the service into an inconsistent state that degrades or interrupts its availability. Because the attack vector is local (AV:L), remote exploitation is not indicated, and no public exploit has been identified in the available data. The exact trigger mechanics are not described in the sources beyond the CWE-362 race-condition classification. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 02, 2026
A race condition (CWE-362) in the Huawei HarmonyOS location service module lets a local, low-privileged user or app disrupt the service, with the assessed impact limited to availability rather than confidentiality or integrity. The flaw is only reachable with local access to the device (AV:L) and depends on winning a timing window (assessed AC:H), so it is not remotely exploitable and successful triggering requires persistence or repeated attempts. No public exploit code has been identified and the issue is not in CISA KEV; Huawei has published October 2026 consumer, wearable and laptop security bulletins that should be consulted for fixed builds, although specific affected and fixed HarmonyOS versions are not enumerated in the available data.
RemediationAI
No vendor-released patch version is identified in the provided data, so the authoritative remediation path is to check the three Huawei October 2026 security bulletins - consumer devices (https://consumer.huawei.com/en/support/bulletin/2026/10/), wearables (https://consumer.huawei.com/en/support/bulletinwearables/2026/10/) and laptops (https://consumer.huawei.com/en/support/bulletinlaptops/2026/10/) - for the fixed HarmonyOS build matching each device model, and to apply the listed update when it becomes available for that branch. Until a fixed build is confirmed for a given device, the exposure is bounded by the local attack vector and availability-only impact: reducing the set of installed apps to trusted sources and auditing which apps hold location permissions limits the number of low-privileged local contexts able to interact with the location service, at the cost of reduced app flexibility and additional administrative effort on managed fleets. Because the flaw is a timing-dependent race condition, there is no configuration switch or port-level workaround identified in the available sources, and no claim is made that such a workaround exists.
Affected VersionsENISA
Affected Packages
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 affected component is the location service module of Huawei HarmonyOS, which brokers location requests between apps and the platform's positioning stack. The root cause class is CWE-362 (concurrent execution using a shared resource with improper synchronization), meaning the service's handling of concurrent access to shared state is not properly serialized; the exact trigger, the specific shared resource involved, and any inter-process or permission-check interaction are not described in the available sources. The CPE entry cpe:2.3:a:huawei:harmonyos:*:*:*:*:*:*:*:* uses a wildcard version, so no precise build range is confirmed, and the three vendor bulletins referenced cover distinct device families (consumer phones, wearables, laptops), implying the fix is distributed across multiple HarmonyOS product branches rather than a single release. The authoritative assessed vector (AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L) indicates a local attacker with low privileges and no user interaction, a high-attack-complexity timing dependency, and availability-only impact; the vendor-supplied description likewise states only that availability may be affected.
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
AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Local-only mobile OS flaw exploited via an on-device app (AV:L/PR:L); race-condition timing window makes reliable triggering harder (AC:H); authoritative impact text limits effect to availability, so C/I set to N and A:L.
Primary rating from Vendor (huawei).
CVSS VectorVendor: huawei
DescriptionCVE.org
Race condition vulnerability in the location service module. Impact: Successful exploitation of this vulnerability may affect availability.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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).
Out-of-bounds heap write in Huawei HarmonyOS WEB module allows unauthenticated remote attackers to execute arbitrary cod
Permission verification vulnerability in the wpa_supplicant module Impact: Successful exploitation of this vulnerability
Permission management vulnerability in the PMS module. Rated critical severity (CVSS 9.8), this vulnerability is remotel
Vulnerability of access permissions not being strictly verified in the APPWidget module.Successful exploitation of this
Vulnerability of permissions not being strictly verified in the window management module.Successful exploitation of this
API permission management vulnerability in the Fwk-Display module.Successful exploitation of this vulnerability may caus
Vulnerability of defects introduced in the design process in the HiviewTunner module. Rated critical severity (CVSS 9.8)
The DP module has a service hijacking vulnerability.Successful exploitation of this vulnerability may affect some Super
Vulnerability of out-of-bounds parameter read/write in the Wi-Fi module. Rated critical severity (CVSS 9.8), this vulner
Vulnerability of commands from the modem being intercepted in the atcmdserver module. Rated critical severity (CVSS 9.8)
Some smartphones have configuration issues. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitab
Some smartphones have the out-of-bounds write vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is r
EUVD-2026-115079
GHSA-279j-x223-5hhm
NVD
CVE.org
Exploit-DB