Is CVE-2026-59098 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-59098 being exploited in the wild.

How severe is CVE-2026-59098?

Medium severity, with a CVSS score of 6.5, published 2 July 2026.

Which products and versions are affected?

LobeHub LobeChat through 2.2.9.

Is there a fix for CVE-2026-59098?

A patch was published on 2026-07-01: Fix merged in GitHub pull request #16594 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-59098 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-59098?

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.

CVE-2026-59098: LobeHub LobeChat broken access control in RAG semantic search

CVE-2026-59098 · Severity: medium · CVSS 6.5 · Published 2026-07-02

LobeChat, an open-source AI chat framework, contains a security flaw in how it handles private documents uploaded by users for AI analysis. An authenticated user can bypass security restrictions to search through and read the contents of documents belonging to other users on the same server. This could lead to the exposure of sensitive information, such as private notes, API keys, or confidential business data stored within the application's knowledge base.

Technologies: LobeHub LobeChat. Vendors: LobeHub.

Quick answers

Is CVE-2026-59098 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-59098 being exploited in the wild.
How severe is CVE-2026-59098?: Medium severity, with a CVSS score of 6.5, published 2 July 2026.
Which products and versions are affected?: LobeHub LobeChat through 2.2.9.
Is there a fix for CVE-2026-59098?: A patch was published on 2026-07-01: Fix merged in GitHub pull request #16594 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-59098 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-59098?: 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 access control vulnerability (IDOR) exists in LobeChat's Retrieval-Augmented Generation (RAG) component. The `semanticSearch` and `semanticSearchForChat` methods in the `ChunkModel` failed to include a `userId` predicate in their database queries. Consequently, an authenticated attacker can perform vector similarity searches against the entire database corpus or specific `fileIds`/`knowledgeIds` belonging to other users. This allows for the retrieval of plain-text chunks, filenames, and metadata from documents the attacker does not own. The issue was addressed by enforcing ownership checks in the `ChunkModel` and scoping knowledge-base file resolution to the caller's `userId`.

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 pull request #16594
2026-07-02: advisory: CVE published and NVD record created

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.