{"answers":{"affected":"2 open source packages ship an affected version, including @lobehub/lobehub. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39411 exists.","fix":"Upgrade @lobehub/lobehub to 2.1.48 or later.","what":"CVE-2026-39411 is a medium-severity authentication bypass vulnerability in lobehub, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-39411 and fix it if it is affected.\n\nWhat it is: CVE-2026-39411 is a medium-severity authentication bypass vulnerability in lobehub, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39411 exists.\n\nAffected packages and fixed versions:\n- @lobehub/lobehub (npm): affected all versions; fixed in 2.1.48\n- @lobehub/lobehub (npm): affected all versions; fixed in 2.1.48\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-39411/ (Markdown: https://insights.sbomify.com/CVE-2026-39411/index.md)","id":"CVE-2026-39411","markdown":"https://insights.sbomify.com/CVE-2026-39411/index.md","name":"CVE-2026-39411","record":{"aliases":["GHSA-5mwj-v5jw-5c97"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"LobeHub web application","requires_auth":"low_privilege","summary":"Attackers can bypass authentication on protected webapi routes by forging the X-lobe-chat-auth header using a hardcoded XOR key.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"lobehub","vendor":"lobehub"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"LobeHub has an unauthenticated authentication bypass on `webapi` routes via forgeable `X-lobe-chat-auth` header","id":"CVE-2026-39411","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"LiquidJS: ownPropertyOnly bypass via sort_natural filter — prototype property information disclosure through sorting side-channel","id":"CVE-2026-39412"},"packages":[{"ecosystem":"npm","fixed":["2.1.48"],"introduced":["0"],"last_affected":[],"package":"@lobehub/lobehub","purl":null,"source":"GHSA-5mwj-v5jw-5c97"},{"ecosystem":"npm","fixed":["2.1.48"],"introduced":["0"],"last_affected":[],"package":"@lobehub/lobehub","purl":"pkg:npm/%40lobehub/lobehub","source":"GHSA-5mwj-v5jw-5c97"}],"prev":{"headline":"Hono has a non-breaking space prefix bypass in cookie name handling in getCookie()","id":"CVE-2026-39410"},"products":["lobehub"],"published":"2026-04-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["lobehub"]},"summary":"Attackers can bypass authentication on protected webapi routes by forging the X-lobe-chat-auth header using a hardcoded XOR key.","url":"https://insights.sbomify.com/CVE-2026-39411/"}