Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInject stored XSS via template-preview/drag-preview
-
DeliveryVictim previews malicious content in renderer
-
ExploitScript calls probeAcpAdapter over desktop:acp-probe IPC
-
ExecutionMain process spawns caller-supplied input.path executable
-
ImpactArbitrary code runs with user privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Dangerous method exposure prevention
|
| Exploitation Conditions | Exploitation requires a chained foothold, not direct remote access: the attacker must first achieve stored cross-site scripting in a renderer through the template-preview or drag-preview feature, and the victim must then preview that attacker-controlled content (UI:A). Once script runs in the renderer, the desktop:acp-probe IPC handler is invokable because it lacks a sender check, letting probeAcpAdapter spawn any executable named in the caller-supplied input.path with the user's privileges. Limiting factors: only EdgeEver Desktop versions 1.92.0 through 1.112.0 are affected; a pre-existing XSS vector is mandatory (there is no standalone network RCE); and active user interaction is needed to trigger the vulnerable preview path. |
| Impact | This is a genuine but conditional risk rather than a drop-everything emergency. The CVSS 4.0 base score of 7.3 (High) reflects an attack vector of AV:N with low complexity (AC:L) but is tempered by an attack requirement (AT:P), low privileges (PR:L), and required active user interaction (UI:A); impact is full compromise of the vulnerable system (VC:H/VI:H/VA:H) with no subsequent-system impact. Critically, this is a chained vulnerability: the RCE is only reachable after an attacker already achieves script execution in a renderer via stored XSS (CWE-749, exposed dangerous IPC method lacking a sender check). No EPSS score was provided in the input, the CVE is NOT listed in CISA KEV, and no public exploit was flagged - so exploitation status is 'no public exploit identified at time of analysis.' However, the fixing commit (6b5027e) and GitHub issues are public, which lowers the barrier to developing a working exploit. Weighing these signals together: the severity is real for any EdgeEver Desktop user on 1.92.0-1.112.0, but the multi-stage requirement (XSS foothold + user interaction) plus the product's apparently small deployment footprint make widespread, automated exploitation unlikely. Prioritize patching for actual EdgeEver users; deprioritize relative to internet-facing or ubiquitous-software CVEs. |
| Exploit ScenarioDerived | An attacker plants a malicious payload in a template-preview or drag-preview surface that triggers stored cross-site scripting inside EdgeEver Desktop's renderer. When the victim previews that content, the injected script invokes probeAcpAdapter over the unguarded desktop:acp-probe IPC handler with a crafted input.path, causing the Electron main process to spawn that executable with the user's privileges. No public proof-of-concept was identified, though the public patch commit discloses the vulnerable code path. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Arbitrary local program execution is possible in EdgeEver Desktop 1.92.0 through 1.112.0 because the desktop:acp-probe IPC handler performs no sender validation and spawns whatever executable path is supplied in the caller's input.path, running it with the victim user's privileges. This is not a standalone network RCE: an attacker must first land stored cross-site scripting in a renderer through the template-preview or drag-preview feature, and the victim must then preview that attacker-controlled content so the renderer script can invoke probeAcpAdapter (CVSS v4.0 7.3; independent assessment CVSS v3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H). No public exploit code and no CISA KEV listing were identified at time of analysis; an upstream fix commit has been referenced, but no patched release version has been independently confirmed.
RemediationAI
Upstream fix available (PR/commit); released patched version not independently confirmed. The corrective commit is https://github.com/tianma-if/edgeever/commit/6b5027e8b4becbee0c0de7cd1a3d04af78ca87ca, which adds sender validation to every ACP IPC handler, introduces validateTrustedAcpPath in apps/desktop/src/main/acp-path-store.mjs (realpath resolution, exclusion of the client data directory, isFile and non-world/group-writable checks), and moves custom executable selection behind a focused-window desktop:acp-choose-path handler limited to the antigravity adapter - deploy a build containing this commit, and treat any EdgeEver Desktop build newer than 1.112.0 as patched only after verifying the changelog, since no fixed version number was published in the supplied data. Until a patched release is confirmed, apply compensating controls with their trade-offs: stop opening or previewing untrusted, imported, or externally sourced templates and dragged content, which removes the stored-XSS foothold but blocks legitimate template workflows; if the application supports it, run the renderer with sandboxing and context isolation enabled and deny Node integration in renderers, which may break preview rendering features; restrict the OS account running EdgeEver so it cannot execute arbitrary binaries outside expected install directories (application whitelisting/AppLocker or equivalent), which is effective against the spawn step but requires endpoint policy change and can break legitimate ACP adapter launches; and monitor process-creation telemetry for EdgeEver child processes spawning shells or binaries outside its own install path, accepting that this is detection rather than prevention. References: https://www.vulncheck.com/advisories/edgeever-desktop-1.92.0-through-1.112.0-local-program-execution-via-acp-ipc, https://github.com/tianma-if/edgeever/issues/532, https://github.com/tianma-if/edgeever/issues/546.
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
EdgeEver Desktop is an Electron-style application that bridges its renderer UI to a Node.js main process through IPC handlers registered in apps/desktop/src/main/acp-host.mjs. The affected code exposes ACP (agent client protocol) adapter management methods over the desktop:acp-probe channel, and the handler forwards caller-controlled input directly into the runtime's probeAdapter/resolveCommand logic, which spawns the referenced binary as a child process. The root cause is CWE-749 (Exposed Dangerous Method or Function): a privileged main-process capability - launching an OS-level executable - is reachable from the renderer without verifying that the sender is a trusted, expected origin, and without constraining the executable path. The referenced upstream fix illustrates the intended trust model: it adds sender checks via allowPrompt(event.sender, event) on probe/list/prompt/cancel, introduces apps/desktop/src/main/acp-path-store.mjs with validateTrustedAcpPath (realpath resolution, rejection of paths inside EdgeEver's client data directory, isFile check, and a group/other-writable mode check on non-Windows platforms), routes custom paths through a new desktop:acp-choose-path handler that only accepts a focused window and the antigravity adapter id, and validates stored paths before reuse. This confirms the vulnerability class is an unvalidated renderer-to-main IPC bridge rather than a memory-safety flaw.
Know when Electron 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
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Reachable only after network-delivered stored XSS (AV:N) needing low-privilege content injection (PR:L) and victim preview (UI:R); yields full code execution as the user (C/I/A:H).
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
DescriptionCVE.org
EdgeEver Desktop 1.92.0 through 1.112.0 contains a remote code execution vulnerability in the desktop:acp-probe IPC handler, which lacks a sender check and spawns a caller-supplied input.path executable. Attackers with script execution in a renderer, such as via template-preview or drag-preview stored cross-site scripting, can call probeAcpAdapter to launch local executables with the user's privileges.
Executive ViewAI
EdgeEver Desktop versions 1.92.0 through 1.112.0 contain a high-severity flaw that allows an attacker to execute arbitrary programs with the victim user's privileges after the user previews malicious content. Any employee using an affected version is at risk of workstation compromise, which could lead to data theft, unauthorized access to internal systems, and operational disruption. Although there is no public exploit identified at time of analysis, leadership should act promptly because the vulnerability requires only authenticated access and user interaction, making it a realistic threat for day-to-day business use.
Disable template-preview and drag-preview features; restrict previewing of untrusted content; enforce least privilege for EdgeEver Desktop users; monitor for unexpected process creation from the application; consider application allowlisting to block execution of unauthorized binaries. No vendor-released patch identified at time of analysis.
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
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
GitHub Electron versions 1.8.2-beta.3 and earlier, 1.7.10 and earlier, 1.6.15 and earlier has a vulnerability in the pro
Cross-site scripting in DeepChat's Mermaid diagram renderer escalates to full remote code execution on affected desktop
Remote code execution in DeepChat 0.5.1 and below is possible through a cross-site scripting flaw in Mermaid diagram ren
Stored cross-site scripting in SiYuan through 3.8.4 lets an attacker who can set a notebook name containing an HTML payl
GitHub Electron before 1.6.8 allows remote command execution because of a nodeIntegration bypass vulnerability. Rated hi
GitHub Electron 1.7.15, 1.8.7, 2.0.7, and 3.0.0-beta.6, in certain scenarios involving IFRAME elements and "nativeWindow
Electron version 1.7 up to 1.7.12; 1.8 up to 1.8.3 and 2.0.0 up to 2.0.0-beta.3 contains an improper handling of values
electron-updater allows for automatic updates for Electron apps. Rated high severity (CVSS 7.5), this vulnerability is r
Cross-origin read bypass in Electron's custom protocol handler exposes sensitive application data to remote pages via fe
Native code execution outside the Chromium sandbox is achievable in Electron prior to 39.8.9, 40.9.2, 41.2.1, and 42.0.0
In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass. Rated critical severity
Privilege escalation in the Electron framework lets a <webview> guest grant itself Node.js integration inside its Web Wo
EUVD-2026-97879
GHSA-x8jx-mq2j-m3pv
NVD
CVE.org
EPSS
Exploit-DB