GHSA-5mwj-v5jw-5c97: LobeHub: Unauthenticated authentication bypass on `webapi` routes via forgeable `X-lobe-chat-auth` header
Summary
LobeHub's webapi routes use a client-controlled header called `X-lobe-chat-auth` for authentication, but it's only XOR-obfuscated (a simple reversible encoding) with a hardcoded key that's visible in the code. An attacker can forge this header to bypass authentication and access protected routes like chat, model listing, and image generation without logging in, potentially using the server's API credentials or impersonating other users.
Solution / Mitigation
Update to LobeHub version 2.1.48 or later, which patches this vulnerability. According to the advisory, the fix involves: stopping use of `X-lobe-chat-auth` as an authentication token, removing the simple apiKey truthiness check as an auth decision, and requiring a real server-validated session, OIDC token (a standard authentication protocol), or validated API key for all protected webapi routes. If client payloads are still needed, they should be signed server-side with an HMAC (a cryptographic signature) or replaced with a normal session-bound backend lookup.
Vulnerability Details
EPSS: 0.0%
Yes
April 8, 2026
Classification
Affected Vendors
Affected Packages
Related Issues
CVE-2026-34371: LibreChat is a ChatGPT clone with additional features. Prior to 0.8.4, LibreChat trusts the name field returned by the e
CVE-2024-27444: langchain_experimental (aka LangChain Experimental) in LangChain before 0.1.8 allows an attacker to bypass the CVE-2023-
Original source: https://github.com/advisories/GHSA-5mwj-v5jw-5c97
First tracked: April 8, 2026 at 02:00 PM
Classified by LLM (prompt v3) · confidence: 85%