CVE-2026-39417: MaxKB: RCE via MCP stdio command injection in workflow engine
MaxKB is an open-source AI assistant for enterprise. Versions 2.7.1 and below contain an incomplete fix for CVE-2025-53928, where a Remote Code Execution vulnerability still exists in the MCP node of the workflow engine. MaxKB only restricts the referencing code path (loading MCP config from the database). The else branch, responsible for loading mcpservers directly from user-supplied JSON remains completely unpatched. Since mcpsource is an optional field (required=False), an attacker can simply omit it or set it to any non-referencing value to bypass the fix. By calling the workflow creation API directly with a crafted JSON payload, an attacker can inject a complete MCP node configuration with stdio transport, arbitrary command, and args — achieving RCE when the workflow is triggered via chat. This issue has been fixed in version 2.8.0.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39417?
CVE-2026-39417 has a high severity rating due to the potential for Remote Code Execution.
How do I fix CVE-2026-39417?
To fix CVE-2026-39417, upgrade MaxKB to version 2.8.0 or higher.
What versions of MaxKB are affected by CVE-2026-39417?
MaxKB versions 2.7.1 and below are affected by CVE-2026-39417.
What type of vulnerability is CVE-2026-39417?
CVE-2026-39417 is a Remote Code Execution vulnerability.
Is there a workaround for CVE-2026-39417?
No official workaround is provided for CVE-2026-39417, so upgrading is the recommended solution.