# CVE-2026-79917: MaxKB: Chat share-link endpoint missing owner check: a chat token can publish another user's conversation

> Attackers can expose other users' private AI conversations and files by exploiting a missing ownership check in the chat sharing endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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:** 21 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-m8gr-554p-8r82

## What is CVE-2026-79917?

CVE-2026-79917 is a medium-severity missing authorization vulnerability in 1Panel-dev MaxKB, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MaxKB is an open-source AI assistant for enterprise. In 2.7.0 through 2.10.4-lts, POST /chat/api/{application_id}/chat/{chat_id}/share_chat verifies that a conversation exists but does not verify that it belongs to the authenticated chat_user_id or to the application bound to the caller's token. An attacker with any chat token and a known victim chat_id can create an unauthenticated public ChatShareLink exposing the victim's conversation and can create PublicFileAccess state that makes associated files retrievable without credentials, with no available revoke path. No fixed version is available as of this review.

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

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


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

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

## Is CVE-2026-79917 being exploited?

There is no known exploitation of CVE-2026-79917 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79917 is a medium-severity missing authorization vulnerability in 1Panel-dev MaxKB, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79917 in the wild and no public exploit code.

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

## Sources

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

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