CVE-2026-53710

10.0

IBM · mcp-context-forge

An unauthenticated code injection vulnerability in the python_sandbox_server allows attackers to execute arbitrary OS commands via the execute_code MCP tool.

Executive summary

An unauthenticated remote code execution vulnerability in the IBM mcp-context-forge AI gateway poses a critical risk of full system compromise.

Vulnerability

The python_sandbox_server component fails to implement necessary guards on attribute access, allowing attackers to bypass validation and invoke sensitive functions like subprocess.Popen. This enables unauthenticated attackers to execute arbitrary system commands with the privileges of the underlying server process.

Business impact

Successful exploitation grants an attacker complete control over the affected server, leading to potential data exfiltration, lateral movement within the network, and the disruption of critical AI services. Given the CVSS score of 10.0, this vulnerability represents the highest level of risk, as it is both remotely exploitable and does not require authentication.

Remediation

Immediate Action: Update the mcp-context-forge python_sandbox_server component to version 1.0.2 or later immediately.

Proactive Monitoring: Monitor server logs for unexpected subprocess executions or unusual calls to the execute_code tool.

Compensating Controls: If an immediate update is not feasible, restrict network access to the HTTP/SSE transport interface to trusted internal segments only, or transition to stdio-only deployments to reduce the attack surface.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

This vulnerability is critical and requires immediate attention due to the potential for unauthenticated remote code execution. Administrators should prioritize upgrading to version 1.0.2 across all affected environments to eliminate the underlying code injection vector. Failure to remediate this issue exposes the infrastructure to total system compromise.

More IBM CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources