CVE-2026-129998
MaxKB tool parameter validators executed stored JavaScript
1Panel-dev · MaxKB
First documented disclosure · Review checkpoint
Summary
Low-privilege tool authors could store code that runs when the initialization form opens.
Severity and exploitation evidence
High · 7.3/10 · CVSS 3.1. Severity source.
Exploitation not established: Public evidence describes a weakness, source correction or controlled demonstration; malicious exploitation against users is not established.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Stored props_info.rules validator strings are passed to eval during rendering.
Conditions required
Authenticated default USER role can create/edit a tool; the malicious Init Param form must render.
Potential impact
Confirmed script execution in the creating account’s MaxKB origin; cross-user token theft is plausible only if another authorized editor renders it.
Affected versions and configurations
Before 2.10.7-lts.
Fix and mitigation status
2.10.7-lts.
Practical next steps
Upgrade; audit untrusted tool parameter definitions.
Operating lesson
Represent validation as constrained data rather than stored executable code.
Evidence and limits
The researcher verified an alert in the author’s own Debug screen, not cross-account execution or credential exfiltration. Public PR7257 opened October 9; advisory October 16. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 3.1 7.3.
Sources
- GitHub_M CVE authority record
Primary source ·
- MaxKB original advisory
Primary source ·
- Public corrective change
Primary source ·