EdgeEver Desktop EUVD-2026-97882

Exploitation requires a victim running EdgeEver Desktop 1.6.26 through 1.112.0 to render attacker-supplied content (the description cites a note-template preview) that embeds a URL using userinfo syntax placed after the trusted dev-server prefix, so the vulnerable string-prefix match in the will-navigate allowlist accepts it while the true origin is attacker-controlled. Limiting factors: the attack needs user interaction (UI:A) - the victim must open or preview the crafted content - and the attacker must first get that content into the app, implying a low-privileged authenticated/collaboration foothold (PR:L); it does not work purely remotely against a default install with no victim action.

The source CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N) yields 8.4 (High), driven by high confidentiality and integrity impact - a successful bypass hands the attacker the edgeeverDesktop bridge including the session token, sidecar RPC, and ACP channels, which can escalate to command execution via ACP adapters. However, two metrics meaningfully temper real-world urgency: UI:A means the victim must actively render attacker-controlled content (e.g., preview a malicious note-template), and PR:L means the attacker needs a low-privileged foothold to deliver that content into the app. No EPSS score, KEV listing, or confirmed public POC is present in the input, so there is no signal of active or widespread exploitation - the only exploit-adjacent artifact is the public fix commit, which paired with the detailed technique (userinfo-syntax URL after the dev-server prefix defeating string-prefix allowlist matching) lowers the barrier to writing a working exploit. CWE-863 (incorrect authorization) is consistent with the described will-navigate allowlist bypass. Net: a genuinely serious client-side authorization flaw, but gated by user interaction and content delivery and affecting a niche product, so it is a patch-promptly issue rather than an emergency internet-wide threat. Note: no EPSS was provided, so exploitation probability cannot be quantified from the input.

An attacker places a note-template (or other previewable content) containing a crafted link such as https://<dev-server-prefix>@attacker.example/ that satisfies EdgeEver's string-prefix allowlist check while actually resolving to an attacker origin. When the victim previews it inside EdgeEver Desktop, the main window navigates to the attacker's page, which now runs with access to the edgeeverDesktop preload bridge and can read the session token and drive sidecar RPC and ACP channels. No public exploit is identified in the input, though the fix commit and the described userinfo technique make reproduction straightforward.