# CVE-2026-77523: MaxKB: Cross-workspace model parameter form write

> Authenticated users can read or modify model parameters in other workspaces by manipulating model IDs, bypassing workspace isolation controls.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **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-g888-8cvh-9284

## What is CVE-2026-77523?

CVE-2026-77523 is a high-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. In version 2.10.3-lts and earlier, the model parameter form route authorizes the path workspace but ModelSerializer.ModelParams loads and saves a Model by id alone without including workspace_id in the query. An authenticated user with model read permission in an attacker-controlled workspace can supply a known victim model_id to read or overwrite the victim's model_params_form in another workspace, potentially altering workflows that use those defaults. No fixed version is available as of this review.

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

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


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

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

## Is CVE-2026-77523 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77523 is a high-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: There is no known exploitation of CVE-2026-77523 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-77523/ (Markdown: https://insights.sbomify.com/CVE-2026-77523/index.md)
```

## Sources

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

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