Summary
CVE-2026-77521 is a critical OS command injection vulnerability in MaxKB, an open-source AI assistant platform, affecting versions prior to 2.10.5-lts. MaxKB assistants configured with a tool, MCP tool, skill, or sub-application route chat through an agent backend that exposes an unrestricted shell "execute" tool without requiring human approval, allowing untrusted chat input or ingested content to trigger arbitrary command execution. The flaw carries the maximum CVSS score of 10.0 due to its network exploitability, lack of required privileges, and full impact on confidentiality, integrity, and availability.
Technical details
- Root cause: MaxKB assistants with an attached tool, MCP tool, skill, or sub-application use a
SandboxShellBackendthat automatically exposes anexecuteshell tool alongside other file/shell utilities; this tool is never excluded from the assistant’s available tools and is omitted from the set of actions requiring human ("interrupt_on") approval before execution. - Trigger conditions: An attacker who can inject content into a chat session or into data later ingested by the assistant (indirect prompt injection) can instruct the underlying model to invoke the
executetool, causing shell command execution without any operator confirmation. - Deployment-specific impact: In source/bare-metal deployments where the
MAXKB_SANDBOXsetting is not enabled (it is off by default), commands run directly on the host as the application user via a shell-invoked subprocess call. In the official container image, neither Dockerfile defines a non-rootUSER, and the sandbox wrapper itself invokes a shell using a string command, so shell metacharacters and redirection can be used to escape the intended sandbox restrictions and execute as root. - Attack vector: Network-based, no authentication or user interaction beyond the ability to submit chat content or ingested data required (AV:N/AC:L/PR:N/UI:N).
- Impact: Full compromise of confidentiality, integrity, and availability of the host running MaxKB, including in multi-tenant or publicly exposed chatbot deployments.
Affected software
- MaxKB (1Panel-dev) versions v2.10.3-lts and earlier, and all prior releases up to and including that version
- Applies to assistants that have a tool, MCP tool, skill, or sub-application attached, which routes chat through the vulnerable shell backend
Severity
- CVSS v3.1 Base Score: 10.0 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Upgrade MaxKB to v2.10.5-lts or later, which fixes the unrestricted shell tool exposure.
- If immediate patching is not possible:
- Disable or remove tools, MCP tools, skills, and sub-applications from assistants that do not strictly require shell/file execution capability.
- Ensure
MAXKB_SANDBOXis enabled for all deployments so shell execution is confined to a sandboxed context. - For containerized deployments, avoid running the MaxKB container as root; apply a non-root
USERdirective where possible. - Restrict network exposure of MaxKB chat interfaces to trusted users only, and avoid exposing assistants with attached tools to public or untrusted input until patched.

