# CVE-2024-32965: ssrf vulnerability in lobe-chat

> Unauthenticated attackers can exploit SSRF in Lobe Chat to scan internal networks and leak sensitive information by modifying proxy headers.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-2xcc-vm3f-m8rw

## What is CVE-2024-32965?

CVE-2024-32965 is a high-severity server-side request forgery vulnerability in lobehub lobe-chat, published on 26 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lobe Chat is an open-source, AI chat framework. Versions of lobe-chat prior to 1.19.13 have an unauthorized ssrf vulnerability. An attacker can construct malicious requests to cause SSRF without logging in, attack intranet services, and leak sensitive information. The jwt token header X-Lobe-Chat-Auth strored proxy address and OpenAI API Key, can be modified to scan an internal network in the target lobe-web environment. This issue has been addressed in release version 1.19.13 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

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

## Which versions are affected by CVE-2024-32965?

2 open source packages ship an affected version, including @lobehub/chat. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@lobehub/chat` | npm | All versions | 1.19.13 |
| `@lobehub/chat` | npm | All versions | 1.19.13 |

Products: Lobehub Lobe Chat.

## How do I fix CVE-2024-32965?

Upgrade @lobehub/chat to 1.19.13 or later.

## Is CVE-2024-32965 being exploited?

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

## Other vulnerabilities in lobehub lobe-chat

- [CVE-2024-47066](https://insights.sbomify.com/CVE-2024-47066/): Lobe Chat has insufficient fix for GHSA-mxhq-xw3g-rphc (CVE-2024-32964) (critical 9.0)
- [CVE-2024-32964](https://insights.sbomify.com/CVE-2024-32964/): lobe-chat `/api/proxy` endpoint Server-Side Request Forgery vulnerability (critical 9.0)
- [CVE-2025-59417](https://insights.sbomify.com/CVE-2025-59417/): Lobe Chat Desktop Vulnerable to Remote Code Execution via XSS in Chat Messages (medium 6.8)
- [CVE-2024-37895](https://insights.sbomify.com/CVE-2024-37895/): API Key Leak in lobe-chat (medium 5.7)
- [CVE-2024-24566](https://insights.sbomify.com/CVE-2024-24566/): Lobe Chat unauthorized access to plugins (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32965 and fix it if it is affected.

What it is: CVE-2024-32965 is a high-severity server-side request forgery vulnerability in lobehub lobe-chat, published on 26 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32965 exists.

Affected packages and fixed versions:
- @lobehub/chat (npm): affected all versions; fixed in 1.19.13
- @lobehub/chat (npm): affected all versions; fixed in 1.19.13

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-2024-32965/ (Markdown: https://insights.sbomify.com/CVE-2024-32965/index.md)
```

## Sources

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

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