CVE-2026-39411 | LobeHub up to 2.1.47 /webapi/chat/ improper authentication (GHSA-5mwj-v5jw-5c97)

VDB-356490 · CVE-2026-39411 · GHSA-5MWJ-V5JW-5C97 LOBEHUB UP TO 2.1.47 /WEBAPI/CHAT/ IMPROPER AUTHENTICATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.9 $0-$5k 0.80+ Summaryinfo A vulnerability categorized as critical has been discovered in LobeHub up to 2.1.47. This affects an unknown part of the file /webapi/chat/. The manipulation results in improper authentication. This vulnerability is known as CVE-2026-39411. It is possible to launch the attack remotely. No exploit is available. It is advisable to upgrade the affected component. Detailsinfo A vulnerability classified as critical has been found in LobeHub up to 2.1.47. Affected is an unknown functionality of the file /webapi/chat/. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes: LobeHub is a work-and-lifestyle space to find, build, and collaborate with agent teammates that grow with you. Prior to 2.1.48, the webapi authentication layer trusts a client-controlled X-lobe-chat-auth header that is only XOR-obfuscated, not signed or otherwise authenticated. Because the XOR key is hardcoded in the repository, an attacker can forge arbitrary auth payloads and bypass authentication on protected webapi routes. Affected routes include /webapi/chat/[provider], /webapi/models/[provider], /webapi/models/[provider]/pull, and /webapi/create-image/comfyui. This vulnerability is fixed in 2.1.48. The advisory is available at github.com. This vulnerability is traded as CVE-2026-39411 since 04/07/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. Upgrading to version 2.1.48 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 3327b293d66c013f076cbc16cdbd05a61a3d0428 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Name LobeHub Version 2.1.0 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.1.7 2.1.8 2.1.9 2.1.10 2.1.11 2.1.12 2.1.13 2.1.14 2.1.15 2.1.16 2.1.17 2.1.18 2.1.19 2.1.20 2.1.21 2.1.22 2.1.23 2.1.24 2.1.25 2.1.26 2.1.27 2.1.28 2.1.29 2.1.30 2.1.31 2.1.32 2.1.33 2.1.34 2.1.35 2.1.36 2.1.37 2.1.38 2.1.39 2.1.40 2.1.41 2.1.42 2.1.43 2.1.44 2.1.45 2.1.46 2.1.47 License open-source Website Product: https://github.com/lobehub/lobehub/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.0 VulDB Meta Temp Score: 4.9 VulDB Base Score: 5.0 VulDB Temp Score: 4.8 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 5.0 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Improper authentication CWE: CWE-287 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: LobeHub 2.1.48 Patch: 3327b293d66c013f076cbc16cdbd05a61a3d0428 Timelineinfo 04/07/2026 CVE reserved 04/09/2026 +2 days Advisory disclosed 04/09/2026 +0 days VulDB entry created 04/09/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-5mwj-v5jw-5c97 Status: Confirmed CVE: CVE-2026-39411 (🔒) GCVE (CVE): GCVE-0-2026-39411 GCVE (VulDB): GCVE-100-356490 Entryinfo Created: 04/09/2026 02:50 Changes: 04/09/2026 02:50 (67) Complete: 🔍 Cache ID: 99:3EE:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸