CVE-2026-55608: n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operati

Q: How do I fix CVE-2026-55608?

n8n-mcp: upgrade to 2.57.4. Exact commands for each OS are on this page.

Q: Is CVE-2026-55608 being exploited?

CVE-2026-55608 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-55608 affect?

CVE-2026-55608 affects n8n-mcp. Severity is medium (CVSS 4.2). n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. Prior to 2.57.4, multi-tenant HTTP mode with ENABLE_MULTI_TENANT=true could allow an authenticated tenant to access default-s

Q: How urgent is CVE-2026-55608?

Priority 20/100. No elevated risk signals yet.

Routine

MEDIUM 4.2UPGRADE

CVE-2026-55608 is a medium-severity flaw (CVSS 4.2) affecting n8n-mcp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. Prior to 2.57.4, multi-tenant HTTP mode with ENABLE_MULTI_TENANT=true could allow an authenticated tenant to access default-scope workflow_versions backups instead of being confined to the tenant scope, exposing or deleting workflow-version backups from prior single-tenant deployments or migrations. This issue is fixed in version 2.5

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.2 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-200, CWE-863
Published	2026-07-15
Last modified	2026-10-24

Publisher (CNA): GitHub, Inc. · Vendor: n8n-mcp

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-15 21:16 UTCPublished CVE record published
2026-10-24 21:10 UTCUpdated Record last modified

n8n-mcp n8n-mcp UPGRADE

Affected: < 2.57.4

Fixed in: 2.57.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy n8n-mcp || rpm -q n8n-mcp || n8n-mcp --version

2. UPGRADE to 2.57.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade n8n-mcp

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade n8n-mcp

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-55608?

n8n-mcp: upgrade to 2.57.4. Exact commands for each OS are on this page.

Is CVE-2026-55608 being exploited?

CVE-2026-55608 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-55608 affect?

CVE-2026-55608 affects n8n-mcp. Severity is medium (CVSS 4.2). n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. Prior to 2.57.4, multi-tenant HTTP mode with ENABLE_MULTI_TENANT=true could allow an authenticated tenant to access default-s

How urgent is CVE-2026-55608?

Priority 20/100. No elevated risk signals yet.

Related CVEs

CVE-2026-54052 CRITICAL 9.9 UPGRADE n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operati

References

← Back to latest CVEs