Quick answers
- Is CVE-2025-59417 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-59417 being exploited in the wild.
- How severe is CVE-2025-59417?
- Medium severity, with a CVSS score of 4, published 18 September 2025.
- Which products and versions are affected?
- Lobe Chat Desktop up to 1.129.3; @lobehub/chat (npm) SEMVER:introduced=0,fixed=1.129.4.
- Is there a fix for CVE-2025-59417?
- Yes. @lobehub/chat (npm): upgrade to 1.129.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-59417 attacked?
- It is attacked with local access or over the network, in a web application.
- Am I affected by CVE-2025-59417?
- Check whether you run Lobe Chat Desktop or @lobehub/chat (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @lobehub/chat (npm): upgrade to 1.129.4 or later
npm install @lobehub/chat@1.129.4
Technical details
Lobe Chat Desktop contains a cross-site scripting (XSS) vulnerability in its SVG artifact rendering component, which uses dangerouslySetInnerHTML to render user-supplied SVG content without proper sanitization. An attacker can inject a lobeArtifact element with type="image/svg+xml" containing malicious JavaScript (e.g., via onerror events in SVG img tags) into chat messages through prompt injection, compromised MCP servers, or tool integrations. Once XSS is achieved in the Electron renderer process, the attacker can invoke privileged IPC APIs (specifically openExternalLink) that lack input validation, allowing arbitrary command execution via file:// URIs or shell commands. The vulnerability affects versions up to 1.129.3 and is fixed in 1.129.4.
Affected products
- Lobe Chat Desktop up to 1.129.3
Identifiers
- CVE-2025-59417
- GHSA-m79r-r765-5f9j
Timeline
- 2025-09-18: disclosed
- 2025-09-18: patched: fixed in version 1.129.4