CVE-2026-85621 Details
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.
A vulnerability exists in LobeChat (LobeHub) version 2.2.1, where the application fails to properly verify webhook signatures for incoming messages in the QQ and Feishu chat platform adapters. The webhook route is intentionally left unauthenticated and relies on each adapter to perform signature verification. However, the QQ adapter does not implement any signature verification for dispatched message events, while the Feishu adapter only conducts an optional static-token comparison that is bypassed if no token is configured (which is the default) and does not verify the request body signature even when a token is set. This flaw allows an unauthenticated attacker, aware of the public webhook URL, to send forged messages with a spoofed sender identity and arbitrary content. The recipient's bot processes this attacker-controlled input as if it were a trusted platform message, effectively injecting prompts into the conversation.
To address this vulnerability, implement proper signature verification for incoming webhooks in both the QQ and Feishu adapters. For QQ, verify the Ed25519 signature using the client secret, and for Feishu, compute and verify the Lark request signature over the raw body, making verification mandatory rather than optional.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 4, 2026CISA-ADP
Assessed Sep 8, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/lobehub/lobehub/issues/16538 | CISA-ADP | ExploitIssue TrackingTechnical DescriptionVendor |
| https://github.com/lobehub/lobehub | [email protected] | Source CodeVendor |
| https://github.com/lobehub/lobehub/blob/v2.2.15/packages/chat-adapter-feishu/src/adapter.ts | [email protected] | Source CodeVendor |
| https://github.com/lobehub/lobehub/blob/v2.2.15/packages/chat-adapter-qq/src/adapter.ts | [email protected] | Source CodeVendor |
| https://github.com/lobehub/lobehub/issues/16538 | [email protected] | ExploitIssue TrackingTechnical DescriptionVendor |
| https://www.vulncheck.com/advisories/lobechat-2.2.1-webhook-signature-verification-bypass-qq-feishu | [email protected] | AdvisoryBundleRemedy |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-345 | Insufficient Verification of Data Authenticity | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| LobeHub | <= 2.2.15 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 8, 2026 | CVE Modified | CISA-ADP |
| Sep 4, 2026 | New CVE Received | [email protected] |
Volerion