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.

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

Q: Which products and versions are affected?

LobeHub Lobe Chat < 2.1.48; @lobehub/lobehub (npm) SEMVER:introduced=0,fixed=2.1.48.

Q: 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.

Q: How is CVE-2026-39411 attacked?

It is attacked over the network, in a software library.

Q: 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.

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, Lobehub, @lobehub/lobehub (npm). Vendors: LobeHub, 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
```
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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.