Skip to content
Fencer Intel
high 8.1

CVE-2024-32965 in the critical feed json

ssrf vulnerability in lobe-chat

published last yr. modified 4mo ago also EUVD-2024-3338 , GHSA-2xcc-vm3f-m8rw

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
26.1%
EPSS 26.1% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm @lobehub/chat 1.19.13
  • lobehub lobe_chat 1.19.13

Is CVE-2024-32965 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

26.13% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/lobehub/lobe-chat/security/advisories/GHSA-2xcc-vm3f-m8rw referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:L
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:L
NVD 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Affected packages

ecosystem package affected fixed in
npm @lobehub/chat
<1.19.13
1.19.13

Affected products

  • lobehub lobe-chat
  • lobehub lobe_chat

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.