# CVE-2026-39411: LobeHub authentication bypass via forgeable X-lobe-chat-auth header

Source: https://junglewise.ai/threats/cve-2026-39411-lobehub-authentication-bypass-via-forgeable-x-lobe-chat-auth  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-08. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-39411 · Severity: medium · CVSS 5 · Published 2026-04-08

LobeHub is an AI agent management platform that provides API endpoints for chat, model operations, and image generation. A flaw in the authentication mechanism allows unauthenticated attackers to forge authentication headers using a publicly available XOR key, bypassing login requirements and gaining access to protected API routes. This could allow attackers to use configured API credentials (like OpenAI keys) at the deployer's expense or impersonate legitimate users.

Technologies: [LobeHub Lobe Chat](https://junglewise.ai/threats/technologies/lobe-chat), [Lobehub](https://junglewise.ai/threats/technologies/lobehub), [@lobehub/lobehub (npm)](https://junglewise.ai/threats/technologies/lobehub-lobehub). Vendors: [LobeHub](https://junglewise.ai/threats/vendors/lobehub), [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2026-39411 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-39411 being exploited in the wild.

**How severe is CVE-2026-39411?** Medium severity, with a CVSS score of 5, published 8 April 2026.

**Which products and versions are affected?** LobeHub Lobe Chat < 2.1.48; @lobehub/lobehub (npm) SEMVER:introduced=0,fixed=2.1.48.

**Is there a fix for CVE-2026-39411?** Yes. @lobehub/lobehub (npm): upgrade to 2.1.48 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-39411 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-39411?** Check whether you run LobeHub Lobe Chat, Lobehub or @lobehub/lobehub (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- @lobehub/lobehub (npm): upgrade to 2.1.48 or later

  ```sh
  npm install @lobehub/lobehub@2.1.48
  ```


## Technical details

The vulnerability is an authentication bypass caused by insufficient verification of client-supplied authentication data (CWE-287, CWE-345, CWE-290). The backend accepts an X-lobe-chat-auth header that is only XOR-obfuscated with a static hardcoded key ("LobeHub · LobeHub") found in the repository. The backend decodes this header and treats any truthy apiKey field as sufficient authentication without validating it against a real API key or session. An attacker with knowledge of the XOR key can craft forged payloads such as {"apiKey":"x"} or {"userId":"victim-user-123","apiKey":"x"} to access protected routes including POST /webapi/chat/[provider], GET /webapi/models/[provider], POST /webapi/models/[provider]/pull, and POST /webapi/create-image/comfyui. This requires network access but no prior authentication. The vulnerability was patched in version 2.1.48 by removing the XOR-based authentication mechanism entirely and requiring session/OIDC-based authentication instead.

## Affected products

- LobeHub LobeHub <= 2.1.47

## Identifiers

- CVE-2026-39411
- GHSA-5mwj-v5jw-5c97

## Timeline

- 2026-04-08: disclosed: Advisory GHSA-5mwj-v5jw-5c97 published
- 2026-04-07: patched: Fix merged in PR #13535, patched in v2.1.48

## References

- [https://github.com/lobehub/lobehub/security/advisories/GHSA-5mwj-v5jw-5c97](https://github.com/lobehub/lobehub/security/advisories/GHSA-5mwj-v5jw-5c97)
- [https://github.com/lobehub/lobehub/pull/13535](https://github.com/lobehub/lobehub/pull/13535)
- [https://github.com/lobehub/lobehub/commit/3327b293d66c013f076cbc16cdbd05a61a3d0428](https://github.com/lobehub/lobehub/commit/3327b293d66c013f076cbc16cdbd05a61a3d0428)
- [https://github.com/lobehub/lobehub](https://github.com/lobehub/lobehub)
- [https://github.com/lobehub/lobehub/releases/tag/v2.1.48](https://github.com/lobehub/lobehub/releases/tag/v2.1.48)

## Related threats

- [LobeHub SSRF and cookie injection in webapi proxy](https://junglewise.ai/threats/cve-2026-54157-lobehub-ssrf-and-cookie-injection-in-webapi-proxy)
- [LobeHub LobeChat XSS to RCE via Electron IPC interface](https://junglewise.ai/threats/cve-2026-42045-lobehub-lobechat-xss-to-rce-via-electron-ipc-interface)
- [LobeHub improper authorization in presigned file upload](https://junglewise.ai/threats/cve-2026-23835-lobehub-improper-authorization-in-presigned-file-upload)
- [Lobe Chat stored XSS in Mermaid artifact renderer escalating to RCE](https://junglewise.ai/threats/cve-2026-23733-lobe-chat-stored-xss-in-mermaid-artifact-renderer-escalating-to)
- [Lobe Chat server-side request forgery in web crawler](https://junglewise.ai/threats/cve-2025-62505-lobe-chat-server-side-request-forgery-in-web-crawler)