---
id: CVE-2026-85621
title: >-
  LobeChat (LobeHub) 2.2.1 does not properly verify inbound chat-platform
  webhook signatures in the QQ and Feishu adapters
summary: >-
  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 a…
severity: medium
cvss: 6.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'
cwe:
  - CWE-345
vendor: lobehub
product: lobehub
affected:
  - lobehub <= 2.2.15
published: '2026-09-04'
updated: '2026-09-24'
sourceUpdated: '2026-09-24T20:43:32.537'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-85621'
references:
  - url: 'https://github.com/lobehub/lobehub'
    label: disclosure@vulncheck.com
  - url: >-
      https://github.com/lobehub/lobehub/blob/v2.2.15/packages/chat-adapter-feishu/src/adapter.ts
    label: disclosure@vulncheck.com
  - url: >-
      https://github.com/lobehub/lobehub/blob/v2.2.15/packages/chat-adapter-qq/src/adapter.ts
    label: disclosure@vulncheck.com
  - url: 'https://github.com/lobehub/lobehub/issues/16538'
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/lobechat-2.2.1-webhook-signature-verification-bypass-qq-feishu
    label: disclosure@vulncheck.com
  - url: 'https://github.com/lobehub/lobehub/issues/16538'
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
  - cve.org
  - exploit-available
epss: 0.00201
epssPercentile: 0.08885
exploitAvailable: true
ssvc:
  exploitation: poc
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-09-08T16:53:46.727439Z'
ingestedAt: '2026-09-08T19:08:49.673Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.