gcdRadar
archive/Patch now/AIR-2024-0140
closedclosed 17 Jun 2024Patch now2 Disclosed vulnerabilityAI

CVE-2024-37895: Lobe Chat API key leak vulnerability

Lobe Chat

Authenticated attackers can obtain backend API keys in Lobe Chat by modifying the base URL and triggering a server-side request. A vendor patch is available.

disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why

CVSS
5.7
EPSS
0.01 · top 54% · 2026-11-13
fix status
Fix status unknown
first report
17 Jun 2024
last update
17 Jun 2024

Timeline · 1

  1. 17 Jun 2024CVE-2024-37895: Lobe Chat API Key Leak

Sources · 1

Advisories and databases

  1. 2024-06-17
    CVE-2024-37895: Lobe Chat API Key Leak
    GitHub Advisory Database · github.com/advisories/GHSA-p36r-qxgx-jq2v

Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.

Classification

AI role
Attack on AI
categories
Data leakInfrastructure vulnerability
severity
2 · Disclosed vulnerability
fix status
Fix status unknown
targets
Framework / tooling
mitre atlas
no technique for these categories
dates
happened 17 Jun 2024 · first reported 17 Jun 2024
origin
GitHub Advisory Database
Vulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
record
confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 07:00Z

Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned

Copy a brief

This record as a short Markdown brief, for a ticket, a chat or a coding agent.

the brief as text
# CVE-2024-37895: Lobe Chat API key leak vulnerability

https://gcdradar.vercel.app/incidents/cve-2024-37895-lobe-chat-api-key-leak-vulnerability · AIR-2024-0140 · closed 2024-06-17

- Lane: Patch now
- Severity: 2 (Disclosed vulnerability)
- Fix status: Fix status unknown
- First reported: 2024-06-17
- AI role: Attack on AI
- Products: Lobe Chat
- CVE ids: CVE-2024-37895
- CVSS: 5.7

## Summary

Authenticated attackers can obtain backend API keys in Lobe Chat by modifying the base URL and triggering a server-side request. A vendor patch is available.

## What to do

No action recorded; read the sources below and the vendor's advisory.

## Latest updates

- 2024-06-17: CVE-2024-37895: Lobe Chat API Key Leak (https://github.com/advisories/GHSA-p36r-qxgx-jq2v)

## Sources

- 2024-06-17 GitHub Advisory Database: CVE-2024-37895: Lobe Chat API Key Leak https://github.com/advisories/GHSA-p36r-qxgx-jq2v

Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.

Related

  1. closed6.9
    Gradio CVE-2024-47868: Gradio component post-processing file leaks

    Patch now · Disclosed · since 10 Oct 2024 · CVE-2024-47868

    AI
  2. closed8.7
    LiteLLM CVE-2024-6587: LiteLLM Server-Side Request Forgery vulnerability

    Patch now · Disclosed · since 13 Sep 2024 · CVE-2024-6587

    AI
  3. closed9.6
    AnythingLLM CVE-2024-0765: AnythingLLM Data Exfiltration Vulnerability

    Patch now · Disclosed · since 3 Mar 2024 · CVE-2024-0765

    AI
  4. closed6.5
    AgentAPI CVE-2025-59956: AgentAPI Client-Side DNS Rebinding Data Exfiltration Flaw

    Patch now · Disclosed · since 30 Sep 2025 · CVE-2025-59956

    AI
  5. closed6.0
    Dify CVE-2025-59422: Broken access control vulnerability in Dify exposes chat messages

    Patch now · Disclosed · since 25 Sep 2025 · CVE-2025-59422

    AI
  6. closed9.6
    Flowise CVE-2025-59434: Cross-tenant environment variable exposure in Flowise Cloud

    Patch now · Disclosed · since 22 Sep 2025 · CVE-2025-59434

    AI