# CVE-2026-59095: LobeChat < 2.2.10-canary.18 - SSRF via importFromUrl and fetchImageFromUrl

> Authenticated attackers can exploit SSRF in LobeChat to access internal services and cloud metadata, leading to data disclosure.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-r2cx-cpfx-9h63

## What is CVE-2026-59095?

CVE-2026-59095 is a high-severity server-side request forgery vulnerability in lobehub, published on 2 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LobeChat before 2.2.10-canary.18 contains a server-side request forgery vulnerability that allows authenticated attackers to direct internal HTTP requests to arbitrary URLs by supplying user-controlled input to the skill import service (importFromUrl) and topic cover update (fetchImageFromUrl) endpoints, which use the global fetch without the project's ssrf-safe-fetch wrapper. Attackers can target internal addresses such as cloud instance metadata endpoints through these unprotected code paths to disclose internal service responses and cloud credentials.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-59095?


## How do I fix CVE-2026-59095?

No fix has been published for CVE-2026-59095 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59095 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59095 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59095 and fix it if it is affected.

What it is: CVE-2026-59095 is a high-severity server-side request forgery vulnerability in lobehub, published on 2 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59095 exists.

Affected product: lobehub. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59095/ (Markdown: https://insights.sbomify.com/CVE-2026-59095/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59095
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59095
- OSV: https://osv.dev/vulnerability/CVE-2026-59095

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59095/
Summaries are generated and may contain mistakes; the official description above is the record.