CVE-2026-129998: In MaxKB, any workspace user could store JavaScript in a custom tool's Init Param validator rule, which ran through eval() when the tool's form opened (fixed 2.10.7-lts)
MaxKB, the open-source enterprise AI assistant from the 1Panel team, lets users create custom tools with Init Param definitions. Before 2.10.7-lts, the validator strings in props_info.rules[] were accepted through POST /admin/api/workspace/{workspace_id}/tool and PUT …/tool/{tool_id}, stored unchanged, and passed to JavaScript eval() when the parameter form rendered. An authenticated user with only the default USER workspace role could store script and have it run in the MaxKB origin by opening the tool's Debug screen, before entering any value. Other users with edit permission on the tool render the same form; the advisory notes that their bearer tokens could be exposed if they open it, but execution in another account was not independently verified. Fixed in 2.10.7-lts.
What it is
Impact is equivalent to stored cross-site scripting in the MaxKB admin UI: script runs with the privileges of whoever renders the form.
The attacker needs a MaxKB account; the lowest default workspace role is enough to create a tool.
Affected: MaxKB <= v2.10.6-lts. v2.10.7-lts was released on 15 October 2026; GitHub published the advisory on 16 October 2026 and NVD the CVE on 20 November 2026.
How to check
- Check the MaxKB version shown in the UI or your container image tag.
- Review custom tools for Init Param validator rules that contain JavaScript rather than simple patterns.
How to fix
- Upgrade MaxKB to v2.10.7-lts or later.
- Remove custom tools from untrusted users that contain script in validator rules, and have admins avoid opening their Debug screens until patched.
docker ps --format '{{.Image}}' | grep -i maxkb