dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-0757

HIGH · 8.8 CVSS v3.0 Published 2026-01-23
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

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
MCP Manager for Claude Desktop execute-command Command Injection Sandbox Escape Vulnerability. This vulnerability allows remote attackers to bypass the sandbox on affected installations of MCP Manager for Claude Desktop. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the processing of MCP config objects. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to escape the sandbox and execute arbitrary code in the context of the current process at medium integrity. Was ZDI-CAN-27810.

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

MCP Manager for Claude Desktop contains a command injection vulnerability in its MCP config object processing. The application fails to validate user-supplied strings before passing them to system calls, allowing attackers to escape the sandbox and execute arbitrary code at medium integrity level. User interaction is required (malicious page/file).

MitigationImplement strict input validation on all MCP config object parameters before system call execution, and ensure all user-supplied data is properly sanitized or whitelisted to prevent command injection.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Verify MCP Manager for Claude Desktop is installed
    Check for the presence of MCP Manager installation on the system. Common locations include the Claude Desktop plugins directory or system application folders. On Windows, check %APPDATA%\Claude\MCP or similar paths. On macOS, check ~/Library/Application Support/Claude/MCP.
    Affected if MCP Manager for Claude Desktop is installed on the system
  2. Determine the installed MCP Manager version
    Locate the MCP Manager application and retrieve its version information. This is typically found in the application's metadata, about section, or version file included with the installation. Compare your installed version to any published version information.
    Affected if The installed version is within an affected range that contains the vulnerability (no specific version range was provided in the CVE data)
  3. Identify if MCP config objects are being processed
    Check for the presence of MCP configuration files or objects that the application uses. These may include JSON, YAML, or other config files in the Claude Desktop configuration directory that define MCP server connections or integrations.
    Affected if MCP config objects are actively used or loaded by the application
  4. Check if system calls are made during config processing
    Inspect application behavior or logs to determine whether MCP config parameters are passed to system calls during processing. This may require monitoring process execution or reviewing application code if accessible.
    Affected if The application executes system calls using data from MCP config objects without validation

A user is affected if they have MCP Manager for Claude Desktop installed, are running a vulnerable version, use MCP config objects, and those configs trigger system calls with unsanitized user-supplied data.

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

Implement strict input validation on all MCP config object parameters before system call execution, and ensure all user-supplied data is properly sanitized or whitelisted to prevent command injection.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0757 — 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-0757 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