# CVE-2026-23522: Lobe Chat has IDOR in Knowledge Base File Removal that Allows Cross User File Deletion

> Authenticated users can delete files from other users' knowledge bases due to missing ownership verification in the file removal API.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2026
- **Updated:** 20 Jan 2026
- **Also known as:** GHSA-j7xp-4mg9-x28r

## What is CVE-2026-23522?

CVE-2026-23522 is a low-severity missing authorization vulnerability in lobehub lobe-chat, published on 19 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LobeChat is an open source chat application platform. Prior to version 2.0.0-next.193, `knowledgeBase.removeFilesFromKnowledgeBase` tRPC ep allows authenticated users to delete files from any knowledge base without verifying ownership. `userId` filter in the database query is commented out, so it's enabling attackers to delete other users' KB files if they know the knowledge base ID and file ID. While the vulnerability is confirmed, practical exploitation requires knowing target's KB ID and target's file ID. These IDs are random and not easily enumerable. However, IDs may leak through shared links, logs, referrer headers and so on. Missing authorization check is a critical security flaw regardless. Users should upgrade to version 2.0.0-next.193 to receive a patch.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes), CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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

2 open source packages ship an affected version, including @lobehub/chat.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@lobehub/chat` | npm | All versions to 1.143.2 | None |
| `@lobehub/chat` | npm | All versions to 1.143.2 | None |

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

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

## Is CVE-2026-23522 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-23522 is a low-severity missing authorization vulnerability in lobehub lobe-chat, published on 19 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23522 exists.

Affected packages and fixed versions:
- @lobehub/chat (npm): affected all versions up to 1.143.2; no fix listed
- @lobehub/chat (npm): affected all versions up to 1.143.2; no fix listed

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-23522/ (Markdown: https://insights.sbomify.com/CVE-2026-23522/index.md)
```

## Sources

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

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