PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

New CVE Detected

CVE-2026-51870 – Remote Code Execution – DeepTutor v1.4.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-51870 is a critical OS command injection vulnerability in DeepTutor v1.4.0, an open-source AI tutoring/agent platform. The flaw resides in the ExecTool.execute function of deeptutor/tutorbot/agent/tools/shell.py, where LLM-generated shell commands are passed directly to a subprocess call without validation, sanitization, or user confirmation. The issue is rated CVSS 9.8 (Critical) and allows an unauthenticated, remote attacker to achieve arbitrary command execution on the host.

Technical details

  • Root cause: TutorBot’s ExecTool.execute function (lines 83–98 of shell.py) passes attacker/LLM-generated command strings directly to asyncio.create_subprocess_shell() with no allowlisting, sanitization, or sandboxing.
  • Trigger conditions: A client connects to the TutorBot WebSocket chat endpoint (/api/v1/tutorbot/<bot_name>/ws) and sends a message/prompt that causes the backing LLM to invoke the shell execution tool; the tool was enabled by default with no confirmation step.
  • Attack vector: Network — no authentication or prior access is required, and no user interaction beyond the attacker’s own crafted prompt is needed.
  • Impact: Full compromise of confidentiality, integrity, and availability via arbitrary OS command execution in the context of the DeepTutor service.

Affected software

  • DeepTutor v1.4.0 (and earlier versions containing the unguarded ExecTool shell execution path)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to DeepTutor v1.4.1 or later, where shell execution is disabled by default (the shell tool is only registered when an administrator explicitly sets allow_shell_exec), filesystem/shell access is confined to the bot workspace, and command deny-listing has been hardened.
  • If immediate patching is not possible: Disable or remove the TutorBot shell execution tool, restrict network exposure of the TutorBot WebSocket endpoint to trusted/internal networks, and avoid enabling allow_shell_exec unless strictly required with additional sandboxing/isolation in place.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge