{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85621 exists.","fix":"No fix has been published for CVE-2026-85621 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85621 is a medium-severity authentication bypass vulnerability in lobehub, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-85621 and fix it if it is affected.\n\nWhat it is: CVE-2026-85621 is a medium-severity authentication bypass vulnerability in lobehub, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85621 exists.\n\nAffected product: lobehub. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-85621/ (Markdown: https://insights.sbomify.com/CVE-2026-85621/index.md)","id":"CVE-2026-85621","markdown":"https://insights.sbomify.com/CVE-2026-85621/index.md","name":"CVE-2026-85621","record":{"aliases":["GHSA-627w-x4jq-g83v"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"LobeChat AI assistant","requires_auth":"none","summary":"Unauthenticated attackers can bypass webhook signature verification in LobeChat to inject forged messages, impersonating trusted users to manipulate the AI agent.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"LobeChat (LobeHub) 2.2.1 does not properly verify inbound chat-platform webhook signatures in the QQ and Feishu adapters. The webhook route (/api/agent/webhooks/:platform) is unauthenticated by design and delegates verification to each adapter; the QQ adapter performs no Ed25519 signature verification on dispatched message events, and the Feishu adapter only performs an optional static-token comparison that is skipped when no token is configured (the default) and is not a body signature. An unauthenticated attacker who knows the public webhook URL can POST forged inbound messages with an attacker-chosen sender identity and arbitrary text, causing the bot owner's agent to process attacker-controlled input and treat the attacker as a trusted platform sender.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"LobeChat 2.2.1 Webhook Signature Verification Bypass QQ Feishu","id":"CVE-2026-85621","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"AppFlowy-Cloud through 0.9.64 Cross-Workspace Collab Read via WebSocket","id":"CVE-2026-85622"},"packages":[],"prev":{"headline":"Postgres MCP Pro 0.3.0 Restricted-Mode Bypass via FROM-Clause Function","id":"CVE-2026-85620"},"products":["lobehub"],"published":"2026-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["lobehub"]},"summary":"Unauthenticated attackers can bypass webhook signature verification in LobeChat to inject forged messages, impersonating trusted users to manipulate the AI agent.","url":"https://insights.sbomify.com/CVE-2026-85621/"}