CVE-2026-129998
High 7.3No known exploitationFix status unknownTitle not yet published
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
No EPSS score available
CISA remediation deadline
Not in the KEV catalog
Description
MaxKB is an open-source AI assistant for enterprise. Prior to 2.10.7-lts, custom Tool Init Param definitions accept attacker-controlled props_info.rules[].validator strings through POST /admin/api/workspace/{workspace_id}/tool and PUT /admin/api/workspace/{workspace_id}/tool/{tool_id}, store them without restriction, and pass them to eval() when the parameter form renders. An authenticated user with the default USER workspace role can store JavaScript and trigger execution by opening the tool's Debug screen before entering or submitting a parameter value. The same Init Param form is exposed to accounts with edit permission on the tool, but execution by a different account was not independently verified. The confirmed script runs in the MaxKB origin; access to another user's bearer token and authenticated account authority is plausible only if that user renders the malicious form. This issue is fixed in version 2.10.7-lts.
Weakness: CWE-95
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
No affected products documented yet.
Timeline
- No dated events documented yet.
Vendor guidance and references
- https://github.com/1Panel-dev/MaxKB/commit/fad2427ab46558c5fad764993a08e3661ab4b7f9 (opens in a new tab)
- https://github.com/1Panel-dev/MaxKB/pull/7257 (opens in a new tab)
- https://github.com/1Panel-dev/MaxKB/releases/tag/v2.10.7-lts (opens in a new tab)
- https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-c4xr-7rr6-43mr (opens in a new tab)