# CVE-2026-77517: MaxKB cross-knowledge IDOR lets a normal user read and modify documents and paragraphs in another knowledge base

> Attackers can read and modify documents in other users' knowledge bases by exploiting missing ownership checks on document and paragraph IDs.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A: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:** 21 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-58cm-c5jq-96vf

## What is CVE-2026-77517?

CVE-2026-77517 is a medium-severity missing authorization vulnerability in 1Panel-dev MaxKB, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MaxKB is an open-source AI assistant for enterprise. From version 2.0.0 through 2.10.2-lts, document and paragraph operate routes authorize only knowledge_id in the request path, then query the target Document by document_id or Paragraph by paragraph_id without confirming that the object belongs to that knowledge base. A normal workspace user with a known victim document or paragraph UUID can use an attacker-owned knowledge-base path to read or modify content in another user's knowledge base. No fixed version is available as of this review.

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

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


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

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

## Is CVE-2026-77517 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77517 is a medium-severity missing authorization vulnerability in 1Panel-dev MaxKB, published on 21 Sep 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-77517 exists.

Affected product: 1Panel-dev MaxKB. 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-77517/ (Markdown: https://insights.sbomify.com/CVE-2026-77517/index.md)
```

## Sources

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

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