CVE-2026-85621
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 5% of all known CVEs.
References
Related Vulnerabilities
Other CWE-345 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-38831 | High | 7.8 | 98% | KEV + Ransom | Fix |
| CVE-2016-4553 | High | 8.6 | 80% | - | Fix |
| CVE-2016-4554 | High | 8.6 | 39% | - | Fix |
| CVE-2023-35719 | Medium | 6.8 | 26% | - | - |
| CVE-2022-26871 | Critical | 9.8 | 20% | KEV | - |
| CVE-2014-4936 | High | 9.3 | 17% | - | - |
Common questions
How do I fix CVE-2026-85621?
No published fix for CVE-2026-85621 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-85621 being actively exploited?
Not that we know of. CVE-2026-85621 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.16% is the estimated probability that it will be exploited in the next 30 days. That is higher than 5% of all scored CVEs.
How severe is CVE-2026-85621?
CVE-2026-85621 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-85621
Markdown
[](https://tridentstack.com/cve/CVE-2026-85621)HTML
<a href="https://tridentstack.com/cve/CVE-2026-85621"><img src="https://tridentstack.com/cve/badge/CVE-2026-85621.svg" alt="CVE-2026-85621"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-08.