Skip to content
Applications

CVE-2026-0757

8.8
High
EPSS 1%Jan 23, 2026

Sandbox escape via command-injection in MCP Manager for Claude Desktop.

common questions

Is CVE-2026-0757 being exploited?

Not confirmed. CVE-2026-0757 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.2% probability of exploitation in the next 30 days.

How severe is CVE-2026-0757?

CVE-2026-0757 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-0757?

Not known from our data. No patch reference has been recorded for CVE-2026-0757, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-0757 affect?

CVE-2026-0757 affects MCP Manager for Claude Desktop. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-0757?

Patch when released; validate MCP config inputs and harden sandbox.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
MCP Manager for Claude Desktop
impact

Remote attacker can escape sandbox and execute arbitrary code in the target process (medium integrity) after user opens malicious content.

action required

Patch when possible

affected versions
MCP Manager for Claude Desktop MCP Manager for Claude Desktop
  • affected1140651e836cabe746f444bdc449cdd2429c4bca

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free