# CVE-2026-77516: MaxKB: Missing per-tool authorization in the agent and workflow tool-dispatch path

> Low-privilege users can execute unauthorized tools and steal credentials by bypassing per-tool permission checks in the agent dispatch path.

- **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:** 28 Sep 2026
- **Also known as:** GHSA-383v-fx78-pphm

## What is CVE-2026-77516?

CVE-2026-77516 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.9.2, a lowest-role workspace member denied access to a tool by WorkspaceUserResourcePermission can still bind its identifier through tool_ids, skill_tool_ids, or mcp_tool_ids and execute it through the agent or workflow dispatch path. The dispatch path does not reapply the per-tool grant enforced by dedicated tool routes, and tool execution decrypts server-side init_params, allowing the caller to receive credentials carried by the denied tool. 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-77516?


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

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

## Is CVE-2026-77516 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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