EUVD-2026-53708
GHSA-7v78-v35x-cqg5
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-accessible renderer, no privileges needed, but user interaction required to trigger media token parsing; only low confidentiality impact with no integrity or availability effect.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
4DescriptionCVE.org
A flaw has been found in netease-youdao LobsterAI 2026.6.10. This affects the function parseMediaTokensFromText of the file src/renderer/services/artifactParser.ts of the component MEDIA Path Handler. This manipulation causes information disclosure. The attack is possible to be carried out remotely. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.
AnalysisAI
Information disclosure in netease-youdao LobsterAI 2026.6.10 exposes sensitive data through manipulation of the MEDIA Path Handler component. The vulnerable function parseMediaTokensFromText in src/renderer/services/artifactParser.ts can be triggered remotely when a user interacts with attacker-controlled content, leaking confidential information such as local file system paths or internal metadata. A publicly available exploit exists via GitHub issue #2176, and the vendor has not responded to coordinated disclosure, leaving no patch available at time of analysis.
Technical ContextAI
LobsterAI is an AI-powered desktop or web application by Netease-Youdao (CPE: cpe:2.3:a:netease-youdao:lobsterai:*:*:*:*:*:*:*:*) that processes AI-generated artifacts through a client-side renderer component - the src/renderer/ path strongly suggests an Electron-based architecture where artifact content is parsed and rendered locally. The function parseMediaTokensFromText in artifactParser.ts is responsible for extracting and resolving media tokens embedded in AI-generated text output, likely to render rich media such as images or audio. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) identifies the root cause class: the media path resolution logic fails to sanitize or restrict what information it surfaces, allowing crafted token sequences to cause the renderer to expose data - such as local filesystem paths, internal configuration values, or session metadata - that should not be accessible from externally supplied input.
RemediationAI
No vendor-released patch has been identified at time of analysis - the vendor was notified through GitHub issue #2176 but has not responded. Users should monitor the project repository at https://github.com/netease-youdao/LobsterAI/ for any patch release or maintainer response. As an immediate compensating control, avoid opening AI-generated artifacts, importing content, or processing media-rich outputs from untrusted or unknown sources within LobsterAI, since user interaction with attacker-controlled content is required to trigger the vulnerability; this reduces exposure without disabling the application entirely, though it does not eliminate risk from trusted-but-compromised content sources. For environments handling sensitive data, consider suspending use of LobsterAI 2026.6.10 until a patch is available, as there is no configuration toggle or feature flag that would disable the vulnerable parseMediaTokensFromText code path based on available information. Deploying endpoint network monitoring to flag anomalous outbound connections originating from the LobsterAI renderer process may help detect active exploitation attempts but does not prevent the underlying disclosure.
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today