Quick answers
- Is CVE-2026-59100 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59100 being exploited in the wild.
- How severe is CVE-2026-59100?
- Medium severity, with a CVSS score of 5, published 2 July 2026.
- Which products and versions are affected?
- LobeHub LobeChat through 2.2.9.
- Is there a fix for CVE-2026-59100?
- A patch was published on 2026-07-01: Fix merged in GitHub PR 16586 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59100 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-59100?
- Check whether you run LobeHub LobeChat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Broken Object Level Authorization (BOLA) vulnerability, also known as Insecure Direct Object Reference (IDOR), exists in LobeChat's database repository layer. Specifically, the 'getGroupAgents', 'updateAgentInGroup', and 'removeAgentsFromGroup' operations in the ChatGroupModel and AgentGroupRepository fail to include a userId predicate in their SQL/ORM queries. An authenticated attacker can exploit this by sending crafted tRPC requests containing arbitrary UUIDs for group identifiers. This allows the attacker to bypass ownership checks to read agent listings, modify agent roles and ordering, or remove agents from groups belonging to other users. The issue was addressed by adding ownership scoping (userId and workspaceId) to the affected database queries.
Affected products
- LobeHub LobeChat through 2.2.9
Timeline
- 2026-06-04: disclosed: Initial researcher report to vendor
- 2026-07-01: patched: Fix merged in GitHub PR 16586
- 2026-07-02: advisory: CVE published and NVD entry created