Skip to content
Applications

CVE-2026-55582

8.4
High
EPSS 0.19%Patch availableAug 26, 2026

Git alias trick allows remote command execution as mcpuser via mcp-shell.

common questions

Is CVE-2026-55582 being exploited?

Not confirmed. CVE-2026-55582 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 0.19% probability of exploitation in the next 30 days.

How severe is CVE-2026-55582?

CVE-2026-55582 is rated High with a CVSS score of 8.4. 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-55582?

Yes. A fix has been recorded for CVE-2026-55582. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-55582 affect?

CVE-2026-55582 affects mcp-shell < 0.6.0, mcp-shell default Docker image, Deployments with /usr/bin/git accessible. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-55582?

Upgrade to mcp-shell 0.6.0; restrict MCP access and remove Git from containers.

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

executive summary
technical analysis
affected
mcp-shell < 0.6.0mcp-shell default Docker imageDeployments with /usr/bin/git accessible
impact

Remote arbitrary OS command execution as the mcp-shell process user via crafted 'git -c alias.pwn' argument over the MCP interface.

action required

Immediate action required

affected versions
sonirico mcp-shell
  • affected< 0.6.0

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