https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-16T12:35:25.412217+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-5941 EUVD-2026-5941 2026-10-16T12:35:30.597023+00:00 EUVD-2026-5941 https://cve.radiocsirt.org/vuln/fkie_cve-2024-37895 fkie_cve-2024-37895 2026-10-16T12:35:30.597064+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-p36r-qxgx-jq2v GHSA-p36r-qxgx-jq2v — Lobe Chat API Key Leak 2026-10-16T12:35:30.597101+00:00

Affected: npm: @lobehub/chat

### Summary

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.

### Details

The attack process is described above.

![image](https://github.com/lobehub/lobe-chat/assets/36695271/df5e0c3c-af28-45c3-959f-182cc9d06680)

### PoC

Frontend: 1. Pass basic authentication (SSO/Access Code). 2. Set the Base URL to a private attack address. 3. Configure the request method to be a server-side request. 4. At the self-set attack address, retrieve the API Key information from the request headers.

Backend: 1. The LobeChat version allows setting the Base URL. 2. There is no outbound traffic whitelist.

### Impact

All community version LobeChat users using SSO/Access Code authentication, tested on version 0.162.13.