CVE-2024-37895Public exploitNetwork attack vector

Backend API key disclosure via attacker-controlled base URL

Published Jun 17, 2024 · Updated Aug 2, 2024

Information disclosure in LobeHub LobeChat before 0.162.25 allows remote authenticated users to obtain the backend API key. The server accepts a frontend-supplied base URL for a server-side model request without an outbound destination allowlist, then sends the API key in a request header to that URL. Exploitation requires SSO or access-code authentication and user interaction to change the base URL; it exposes the configured backend credential without reported data modification or service interruption.

CVSS severity5.7
Medium
EPSS probability0.55%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in LobeHub LobeChat before 0.162.25 allows remote authenticated users to obtain the backend API key. The server accepts a frontend-supplied base URL for a server-side model request without an outbound destination allowlist, then sends the API key in a request header to that URL. Exploitation requires SSO or access-code authentication and user interaction to change the base URL; it exposes the configured backend credential without reported data modification or service interruption.

The record

CVE
CVE-2024-37895
Published
Jun 17, 2024
Updated
Aug 2, 2024
Vendor
LobeHub
Product
LobeChat
Classifications
CWE-918, CWE-200, T1567, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 17, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.162.25

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

LobeHub · LobeChatversion=< 0.162.25

Published CVSS scores

5.7GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1567Exfiltration Over Web Service
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo