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.57.4.
CVE-2026-55608
This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(medium)
- EG Risk
- —
- EPSS
- 20.3%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 17, 2026
Advisory Details (3)
Auto-updated Jul 16, 2026Incorrect authorization can expose default-scope workflow version backups in multi-tenant HTTP mode · Advisory · czlonkowski/n8n-mcp · GitHub
https://github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-2cf7-hpwf-47h9Release v2.57.4
Patch available: czlonkowski/n8n-mcp v2.57.4
https://github.com/czlonkowski/n8n-mcp/releases/tag/v2.57.4commit 1f42899749ed (czlonkowski/n8n-mcp)
Patch available: czlonkowski/n8n-mcp v2.57.4 (contains commit 1f42899749ed)
https://github.com/czlonkowski/n8n-mcp/commit/1f42899749ed0c584fb6b4fd63d75233c3edee59Vendor Advisories for CVE-2026-55608(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| n8n-mcp | — | 2.57.4 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:38 UTCEG score recompute▲ 1.20
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 18:00 UTCNVD updateCVSS v3 → 5.4
- 2026-07-17 13:37 UTCEG score recompute
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-14 20:56 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-863 · CWE-200
Frequently asked(5)
What is CVE-2026-55608?
When was CVE-2026-55608 disclosed?
Is CVE-2026-55608 actively exploited?
What is the CVSS score of CVE-2026-55608?
How do I remediate CVE-2026-55608?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55608
Is Your Infrastructure Affected by CVE-2026-55608?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.