CVE-2026-39420: MaxKB: Sandbox escape via LD_PRELOAD bypass
MaxKB is an open-source AI assistant for enterprise. In versions 2.7.1 and below, an incomplete sandbox protection mechanism allows an authenticated user with tool execution privileges to escape the LDPRELOAD-based sandbox. By env command the attacker can clear the environment variables and drop the sandbox.so hook, leading to unrestricted Remote Code Execution (RCE) and network access. MaxKB restricts untrusted Python code execution via the Tool Debug API by injecting sandbox.so through the LDPRELOAD environment variable. This intercepts sensitive C library functions (like execve, socket, open) to restrict network and file access. However, a patch allowed the /usr/bin/env utility to be executed by the sandboxed user. When an attacker is permitted to create subprocesses, they can execute the env -i python command. The -i flag instructs env to completely clear all environment variables before running the target program. This effectively drops the LDPRELOAD environment variable. The newly spawned Python process will therefore execute natively without any sandbox hooks, bypassing all network and file system restrictions. 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-39420?
CVE-2026-39420 is considered a high severity vulnerability due to the risk of sandbox escape by authenticated users.
How do I fix CVE-2026-39420?
To fix CVE-2026-39420, users should upgrade MaxKB to version 2.8.0 or later.
Who is affected by CVE-2026-39420?
CVE-2026-39420 affects all versions of MaxKB up to and including 2.7.1.
What attack vector is associated with CVE-2026-39420?
The attack vector for CVE-2026-39420 involves authenticated users exploiting the incomplete sandbox protection via LD_PRELOAD.
Can CVE-2026-39420 lead to remote code execution?
Yes, CVE-2026-39420 can potentially lead to remote code execution if the attacker successfully escapes the sandbox.