An authentication-based sandbox escape vulnerability in MaxKB allows authenticated users to execute arbitrary commands and access sensitive data, posing a significant risk to enterprise deployments.

This is a protection mechanism failure (CWE-693) where the LD_PRELOAD sandbox can be bypassed by manipulating call-stack heuristics via Python callbacks. This allows an authenticated workspace member to resolve system calls and interact with the host environment beyond the intended constraints.

Successful exploitation allows an attacker to break out of the containerized environment to read or write files, execute system processes, or perform unauthorized network communications. Given the CVSS score of 6.3, this represents a significant compromise of the application isolation layer, potentially leading to full system compromise or lateral movement within the enterprise network.

Immediate Action: Upgrade MaxKB to version 2.10.6-lts or later immediately to apply the patch that reinforces the sandbox syscall restrictions.

Proactive Monitoring: Review application and system logs for unexpected process execution or unauthorized file access attempts originating from the MaxKB workspace user.

Compensating Controls: Implement strict network segmentation and egress filtering to limit the potential impact if the sandbox is breached.

Public Exploit Available: Unknown

The vulnerability provides a dangerous path for authenticated users to elevate their privileges and escape the designated sandbox environment. Organizations utilizing MaxKB should prioritize the transition to version 2.10.6-lts to ensure that the sandbox protection mechanism is properly secured against these bypass techniques.