dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-30617

HIGH · 8.6 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
LangChain-ChatChat 0.3.1 contains a remote code execution vulnerability in its MCP STDIO server configuration and execution handling. A remote attacker can access the publicly exposed MCP management interface and configure an MCP STDIO server with attacker-controlled commands and arguments. When the MCP server is started and MCP is enabled for agent execution, subsequent agent activity triggers execution of arbitrary commands on the server. Successful exploitation allows arbitrary command execution within the context of the LangChain-ChatChat service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

LangChain-ChatChat 0.3.1 has a remote code execution vulnerability in its MCP STDIO server configuration. Attackers can access the publicly exposed MCP management interface to configure a malicious MCP STDIO server with attacker-controlled commands. When the MCP server is enabled and agent activity triggers its execution, arbitrary commands run within the service context.

MitigationRestrict access to the MCP management interface via authentication or network segmentation, and implement strict validation of MCP server configurations to prevent attacker-controlled command execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify LangChain-ChatChat installation
    Locate the LangChain-ChatChat installation and determine its version by checking version files, package metadata, or the application startup banner. Compare the installed version to 0.3.1.
    Affected if The installed version is 0.3.1 or falls within the affected range.
  2. Verify MCP STDIO server configuration access
    Inspect the network configuration and access controls around the MCP management interface. Determine if it is exposed to untrusted networks or accessible without authentication.
    Affected if The MCP management interface is accessible from public or untrusted networks without proper access controls.
  3. Examine MCP server configuration files
    Review the configuration files that define MCP STDIO servers, typically found in the application config directory or user data directory. Look for any server entries where the command field contains unexpected or suspicious executable paths or arguments.
    Affected if MCP STDIO server configurations contain commands or arguments that were not defined by trusted administrators.
  4. Review application logs for MCP server activity
    Search application logs for entries related to MCP server initialization, particularly stdio server startups. Look for commands being executed that appear user-controlled or unusually formatted.
    Affected if Logs show MCP STDIO servers executing commands that match input from untrusted sources.
  5. Inspect running processes for MCP-related executions
    List running processes on the system hosting LangChain-ChatChat. Identify any processes spawned by the application that execute external commands, especially shell interpreters or unexpected binaries launched in conjunction with MCP server activity.
    Affected if Unexpected command executions are observed in process listings during MCP server operation.

A user is affected if LangChain-ChatChat version 0.3.1 is running with an exposed or accessible MCP management interface that allows configuration of STDIO servers with attacker-controlled commands.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the MCP management interface via authentication or network segmentation, and implement strict validation of MCP server configurations to prevent attacker-controlled command execution.

Have this fixed Scoped from the published advisory
  • Consultation5.0 h
  • Implementation10.0 h
  • Testing5.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30617 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30617 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data