CVE-2026-79918: MaxKB: Sandbox escape via unhooked fexecve
MaxKB is an open-source AI assistant for enterprise. Prior to version 2.10.6-lts, the ToolExecutor LDPRELOAD sandbox hooks execve, execvpe, and execveat to prevent subprocess creation but does not hook fexecve. An authenticated attacker able to execute tool code can call fexecve to start a process outside the sandbox's intended subprocess policy. This issue is fixed in version 2.10.6-lts.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MaxKB: Sandbox escape via unhooked fexecveto a version that resolves this vulnerability.Fixed in 2.10.6-lts
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker must be authenticated and able to execute tool code in MaxKB. The attack can be performed remotely and does not require user interaction.
What capability does exploitation provide?
An attacker can invoke fexecve to create a process outside the ToolExecutor sandbox's intended subprocess-creation policy. The reported impact includes limited effects on confidentiality, integrity, and availability.
Are default deployments affected?
The available information does not state whether tool-code execution is enabled or reachable in the default configuration. Exposure depends on whether authenticated users can execute tool code through ToolExecutor.
What should be done to remediate the issue?
Upgrade MaxKB to version 2.10.6-lts, which fixes the missing fexecve hook. If an immediate upgrade is not possible, restrict access to users who can execute tool code.
How can I determine whether an installation is affected?
Installations running a version earlier than 2.10.6-lts are affected if authenticated users can execute tool code. Version 2.10.6-lts contains the fix.