Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Inconsistency between implementation and spec
|
| Impact | The CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H vector indicates network-based attack with HIGH complexity (AC:H), suggesting exploitation requires specific conditions or multi-step techniques but requires no privileges or user interaction. The High impact across all three categories (CIA triad fully compromised) elevates concern. However, without confirmed EPSS data, KEV/CISA status, or public proof-of-concept availability, the true exploitability remains unclear. The AC:H rating is a mitigating factor—this is not a trivial one-click exploit. Risk priority should account for: (1) whether arkweb is embedded in production systems handling untrusted Wasm code, (2) whether PoC/active exploitation exists, and (3) whether version patching is feasible. For organizations running arkweb in sandboxed contexts or not executing untrusted Wasm, risk is lower; for those processing arbitrary Wasm in security-sensitive contexts, this is critical. |
| Exploit ScenarioDerived | An attacker hosts a malicious website containing carefully crafted WebAssembly code that throws exception types not properly captured by the arkweb v8 module's exception handling mechanism. When a victim visits the site using an arkweb-based browser or embedded WebView, the Wasm code executes and triggers an unhandled exception that bypasses the security boundary. Depending on the uncaught exception's nature, this could: (a) crash the rendering process, enabling denial of service; (b) expose memory contents or execution state in error messages (confidentiality breach); or (c) in worst case, trigger memory corruption if the exception handler improperly manages the call stack. The AC:H rating suggests the attacker must craft the Wasm module and exception type combination precisely, making this a targeted rather than mass-exploitation attack. No confirmed public PoC exists in provided data, but the specific nature of the vulnerability (exception type enumeration) suggests PoC development is feasible for researchers with V8 expertise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 14, 2026
WebAssembly exception handling vulnerability in the arkweb v8 module that prevents proper capture of specific Wasm exception types, potentially allowing attackers to bypass security controls or trigger unexpected application behavior. The vulnerability affects arkweb's V8 integration layer and requires network access but high attack complexity to exploit. While the CVSS score of 8.1 indicates high severity with potential impacts to confidentiality, integrity, and availability, real-world exploitability depends on whether active exploitation or proof-of-concept code exists.
RemediationAI
- Update arkweb to the patched version once released by the arkweb/Chromium project (monitor official release notes). 2. If immediate patching is unavailable, disable WebAssembly execution in arkweb or restrict Wasm code to trusted sources only. 3. Implement strict Content Security Policy (CSP) restrictions preventing untrusted Wasm module loading. 4. Run arkweb in a sandboxed environment with restricted permissions to limit blast radius if exception handling bypass occurs. 5. Monitor application logs for uncaught Wasm exceptions or unexpected crashes correlating with Wasm execution. 6. For embedded implementations, review V8 initialization code to ensure exception handlers are properly registered for all Wasm exception types. Patch availability and specific version numbers require consultation with official arkweb/Chromium security advisories.
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
This vulnerability exists in arkweb's V8 (Chrome's JavaScript/WebAssembly engine) module, specifically in the exception handling mechanisms for WebAssembly. CWE-1068 (Initialization with Hard-Coded Network Resource Configuration Data) suggests the root cause involves improper initialization or configuration of Wasm exception capture handlers, potentially through hardcoded values that fail to accommodate all exception type scenarios. The arkweb project is a Chromium-based embedded browser engine, making this relevant to any system embedding arkweb for WebAssembly execution. The vulnerability manifests when the V8 engine attempts to capture and handle exceptions thrown by Wasm code—certain exception types may bypass the capture mechanism entirely, leading to unhandled exceptions that could crash the application or expose sensitive execution context.
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:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
Wasm exception capture vulnerability in the arkweb v8 module Impact: Successful exploitation of this vulnerability may cause the failure to capture specific Wasm exception types.
Executive ViewAI
A high-severity vulnerability in the arkweb v8 module could allow attackers to bypass WebAssembly exception handling mechanisms, potentially leading to application crashes or unexpected behavior in systems using this component. Organizations deploying arkweb should assess their exposure immediately, as no patch is currently available and the vulnerability requires interim mitigation strategies.
Disable WebAssembly execution in arkweb if not essential to operations; implement Web Application Firewall (WAF) rules to monitor and block suspicious Wasm exception patterns; isolate affected systems through network segmentation to limit lateral movement; apply input validation and sanitization to Wasm modules; monitor application logs for exception handling failures and unexpected terminations; consider running affected workloads in sandboxed or containerized environments with restricted permissions.
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.
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-2025-17086
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB