CVE-2024-37895 API Key Leak in lobe-chat
Authenticated attackers can leak backend API keys by manipulating the frontend base URL, exposing sensitive credentials in Lobe Chat.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2024-37895?
CVE-2024-37895 is a medium-severity vulnerability in lobehub lobe-chat, published on 17 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Lobe Chat is an open-source LLMs/AI chat framework. In affected versions if an attacker can successfully authenticate through SSO/Access Code, they can obtain the real backend API Key by modifying the base URL to their own attack URL on the frontend and setting up a server-side request. This issue has been addressed in version 0.162.25. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Weakness: CWE-200
Which versions are affected by CVE-2024-37895?
2 open source packages ship an affected version, including @lobehub/chat. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@lobehub/chat npm | All versions | 0.162.25 |
@lobehub/chat npm | All versions | 0.162.25 |
Products include Lobehub Lobe Chat.
How do I fix CVE-2024-37895?
Upgrade @lobehub/chat to 0.162.25 or later.
Is CVE-2024-37895 being exploited?
There is no known exploitation of CVE-2024-37895 in the wild and no public exploit code.
Other vulnerabilities in lobehub lobe-chat
- CVE-2024-47066 Lobe Chat has insufficient fix for GHSA-mxhq-xw3g-rphc (CVE-2024-32964)
- CVE-2024-32964 lobe-chat `/api/proxy` endpoint Server-Side Request Forgery vulnerability
- CVE-2024-32965 ssrf vulnerability in lobe-chat
- CVE-2025-59417 Lobe Chat Desktop Vulnerable to Remote Code Execution via XSS in Chat Messages
- CVE-2024-24566 Lobe Chat unauthorized access to plugins
Sources
Also known as GHSA-p36r-qxgx-jq2v.