Quick answers
- Is CVE-2026-59095 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59095 being exploited in the wild.
- How severe is CVE-2026-59095?
- High severity, with a CVSS score of 7.7, published 2 July 2026.
- Which products and versions are affected?
- LobeHub LobeChat before 2.2.10-canary.18.
- Is there a fix for CVE-2026-59095?
- A patch was published on 2026-07-02: Fix merged in PR 16601 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59095 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-59095?
- Check whether you run LobeHub LobeChat 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.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in LobeChat's 'importFromUrl' and 'fetchImageFromUrl' endpoints. These components utilized the global JavaScript 'fetch' function directly on user-supplied URLs instead of using the project's 'ssrf-safe-fetch' wrapper, which implements IP address filtering. An authenticated attacker can exploit this to perform full-read SSRF against internal resources, including cloud instance metadata services (e.g., 169.254.169.254) to extract IAM credentials or probe internal network ports. The vulnerability is resolved in version 2.2.10-canary.18 by routing these requests through the 'ssrfSafeFetch' guard.
Affected products
- LobeHub LobeChat before 2.2.10-canary.18
Timeline
- 2026-07-02: patched: Fix merged in PR 16601
- 2026-07-02: advisory: NVD and VulnCheck advisories published