Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-105135 – Unauthenticated Remote Code Execution – InternLM MindSearch 0.1.0

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

Summary

CVE-2026-105135 is a critical code injection vulnerability in InternLM MindSearch version 0.1.0, affecting the ExecutionAction.run function in the Planner Agent component (mindsearch/agent/graph.py). Manipulation of input arguments allows an attacker to inject and execute arbitrary code, and the flaw can be triggered remotely over the network with no authentication or user interaction required. The vulnerability carries the maximum CVSS v3.1 base score of 10.0 (Critical).

Technical details

  • Root cause: The Planner Agent’s ExecutionAction.run function executes model-generated Python code without adequate validation or sandboxing. Publicly documented proof-of-concept analysis of MindSearch deployments shows the backend extracting the first markdown code fence from an LLM response and running it via exec() with full process globals() and builtins, rather than parsing a scoped, validated action payload.
  • Trigger conditions: An attacker submits a crafted prompt/request that causes the orchestrated LLM to emit attacker-controlled Python code; MindSearch’s agent graph then executes this code as part of normal query handling.
  • Attack vector: Network — the vulnerable /solve endpoint is commonly deployed bound to 0.0.0.0 with no authentication, API key, or session gate, allowing unauthenticated remote attackers to reach the vulnerable code path directly.
  • Impact: Full compromise of confidentiality, integrity, and availability. Code executes in the context of the MindSearch process, which in documented deployments runs as root inside the service container, giving an attacker complete control of the host/container running the affected service.

Affected software

  • InternLM MindSearch — version 0.1.0 (Planner Agent component, mindsearch/agent/graph.py)

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: No vendor-supplied patched version has been confirmed as of this writing; the vendor did not respond to disclosure. Organizations running MindSearch 0.1.0 should check the InternLM/MindSearch GitHub repository for updates addressing this issue and upgrade as soon as a fix is released.
  • If no patch is available:
    • Do not expose the MindSearch /solve endpoint (default port 8002) directly to the internet; bind it to 127.0.0.1 or restrict access to trusted internal networks only.
    • Place the service behind authentication (API key, session, or reverse-proxy enforced auth) since the application itself provides none.
    • Run the MindSearch service as an unprivileged, non-root user inside an isolated, ephemeral container with restricted capabilities to limit the blast radius of any code execution.
    • Replace or wrap unsandboxed exec()-based code execution with a restricted, allowlisted operation dispatcher, and ensure only the intended interpreter action payload (not arbitrary content from the LLM response) is parsed and executed.
    • Monitor for unexpected outbound connections, unauthorized file writes, or anomalous process spawning from hosts running MindSearch.

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