CVE-2026-33224: Authenticated RCE in Bisheng MCP tool configuration
CVE-2026-33224 affects Bisheng and is described in the provided reporting as an authenticated remote command execution vulnerability in Bisheng's MCP tool/server configuration functionality. The issue is tied to unsafe handling of Model Context Protocol (MCP) STDIO-based server configuration, where attacker-controlled command and argument values can be introduced into local process execution without adequate sanitization or restriction. In the reported exploitation pattern, a user able to access Bisheng's MCP configuration workflow can register or modify an MCP tool/server definition so that Bisheng launches an attacker-specified operating system command on the host running the application. The reporting places this issue in a broader family of MCP STDIO command-injection flaws propagated through unsafe SDK and application design. It also notes that Bisheng's open user registration lowers the barrier to obtaining the authenticated access needed for exploitation.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation results in authenticated remote command execution on the Bisheng host. This can allow full system compromise in the context of the Bisheng service account, including execution of arbitrary shell commands, deployment of persistence mechanisms, theft of API keys and application secrets, access to internal data stores and chat/application data, and potential lateral movement from the compromised server into connected internal systems.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, restrict or disable MCP STDIO tool/server configuration in Bisheng, especially for untrusted or self-service users. Disable open registration if not required, tightly limit who can create or edit MCP configurations, and place Bisheng behind network access controls rather than exposing it broadly. Run the service in a hardened sandbox/container with minimal OS privileges, monitor for suspicious child-process creation and MCP tool invocations, and treat all externally supplied MCP configuration as untrusted input.
Remediation
Patch, then assume compromise.
The provided content states that Bisheng has been patched. Remediation is therefore to upgrade to the vendor-fixed version containing the patch for CVE-2026-33224. Based on the described root cause, the fix should prevent user-controlled MCP STDIO configuration from invoking arbitrary commands, for example by removing direct command execution from user-supplied configuration, enforcing strict allowlisting of executable paths and arguments, and validating or sanitizing all MCP tool configuration inputs before process creation.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-33224 exploited in the wild?
- As of May 26, 2026, Mallory has no reports of CVE-2026-33224 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-33224?
- As of May 26, 2026, Mallory has found no public exploit for CVE-2026-33224.
- Is there a patch for CVE-2026-33224?
- The provided content states that Bisheng has been patched. Remediation is therefore to upgrade to the vendor-fixed version containing the patch for CVE-2026-33224.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.