# CVE-2026-59098: LobeChat 2.2.9 - Cross-User Document Disclosure via Unscoped RAG Semantic Search

> Authenticated attackers can access other users' documents and metadata by exploiting missing user-identifier checks in the semantic search functionality.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-w676-mrp6-5fqq

## What is CVE-2026-59098?

CVE-2026-59098 is a high-severity missing authorization vulnerability in lobehub, published on 2 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LobeChat through 2.2.9 contains a broken access control vulnerability in the retrieval-augmented-generation semantic search functionality that allows authenticated attackers to access other users' data by exploiting missing user-identifier predicates in the chunk model semanticSearch method. Attackers can supply arbitrary victim file or knowledge-base identifiers through the chunk retrieval and chat knowledge-base paths to retrieve text content, file names, and metadata belonging to other users.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-59098?


## How do I fix CVE-2026-59098?

No fix has been published for CVE-2026-59098 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59098 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59098 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59098 and fix it if it is affected.

What it is: CVE-2026-59098 is a high-severity missing authorization vulnerability in lobehub, published on 2 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59098 exists.

Affected product: lobehub. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59098/ (Markdown: https://insights.sbomify.com/CVE-2026-59098/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59098
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59098
- OSV: https://osv.dev/vulnerability/CVE-2026-59098

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59098/
Summaries are generated and may contain mistakes; the official description above is the record.