CVE-2026-85621
LobeChat (LobeHub) 2.2.1 does not properly verify inbound …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/lobehub/lobehub
- github.com/lobehub/lobehub/blob/v2.2.15/packages/chat-adapter-feishu/src/adapter.ts
- github.com/lobehub/lobehub/blob/v2.2.15/packages/chat-adapter-qq/src/adapter.ts
- github.com/lobehub/lobehub/issues/16538
- www.vulncheck.com/advisories/lobechat-2.2.1-webhook-signature-verification-bypass-qq-feish
- nvd.nist.gov/vuln/detail/CVE-2026-85621
- cve.org/CVERecord?id=CVE-2026-85621
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.