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.
Published: 2026-09-04
Score: 6.9 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The affected version of the LobeChat application, LobeHub 2.2.1, neglects to enforce cryptographic signature validation for messages received via the QQ and Feishu webhook adapters. The webhook endpoint is intentionally left unauthenticated; however, the adapter code fails to verify Ed25519 signatures or compare a configured static token. This omission allows any party that can reach the public webhook URL to forge inbound messages with a chosen sender identity and arbitrary content, causing the bot agent to treat the attacker as a genuine platform user and process the crafted input.

Affected Systems

The vulnerability targets the LobeHub 2.2.1 release of the LobeChat platform, specifically the QQ and Feishu chat‑adapter modules that handle inbound webhook callbacks. No other product versions are listed in the CNA data.

Risk and Exploitability

The flaw has a CVSS score of 6.9, indicating moderate severity. The EPSS score is not available, and the issue is not listed in CISA KEV. An attacker only needs to know the public webhook URL; no authentication is required. By sending unauthenticated POST requests to the "/api/agent/webhooks/:platform" endpoint, the attacker can exploit the missing verification to inject counterfeit messages, potentially altering the behavior of the bot or executing commands on the agent machine.

Generated by OpenCVE AI on September 4, 2026 at 16:01 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to the latest LobeHub release that includes proper signature verification for QQ and Feishu webhooks.
  • Configure a static token (or enable Ed25519 signature verification) for the QQ and Feishu adapters before deploying the bot.
  • Restrict access to the "/api/agent/webhooks/:platform" endpoint by placing it behind authentication or network firewall rules so that only the webhook provider can reach it.

Generated by OpenCVE AI on September 4, 2026 at 16:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 14:45:00 +0000

Type Values Removed Values Added
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.
Title LobeChat 2.2.1 Webhook Signature Verification Bypass QQ Feishu
First Time appeared Lobehub
Lobehub lobehub
Weaknesses CWE-345
CPEs cpe:2.3:a:lobehub:lobehub:*:*:*:*:*:*:*:*
Vendors & Products Lobehub
Lobehub lobehub
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

cvssV4_0

{'score': 6.9, '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'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-04T14:32:12.595Z

Reserved: 2026-09-04T11:03:33.315Z

Link: CVE-2026-85621

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T15:17:42.293

Modified: 2026-09-04T15:17:42.293

Link: CVE-2026-85621

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T16:15:05Z

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity