<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T09:36:28.259930+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/brew-n8n-mcp-cve-2026-55608</id>
    <title>BREW-n8n-mcp-CVE-2026-55608 — n8n-MCP: Incorrect authorization can expose default-scope workflow version backups in multi-tenant HTTP mode</title>
    <updated>2026-10-05T09:36:28.262374+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: n8n-mcp</p>
<p>## Summary</p>
<p>In multi-tenant HTTP mode (`ENABLE_MULTI_TENANT=true`), an authenticated tenant could, under certain conditions, reach n8n-mcp's local default-scope `workflow_versions` backups instead of being confined to its own tenant scope. This affects n8n-mcp's own local workflow-version storage, not a normal n8n API capability.</p>
<p>## Impact</p>
<p>An authenticated MCP HTTP tenant could read or delete workflow-version backups stored in the default (single-tenant) scope — for example backups left from a prior single-tenant deployment or a migration period. Workflow snapshots may contain sensitive workflow configuration depending on their contents. Single-tenant and stdio deployments are not affected.</p>
<p>## Affected versions</p>
<p>`&lt;= 2.57.3`</p>
<p>## Patched version</p>
<p>`2.57.4`</p>
<p>## Remediation</p>
<p>Upgrade to n8n-mcp `2.57.4` or later. The fix requires a complete tenant context in multi-tenant mode and fails closed for workflow-version access that cannot be attributed to a specific tenant.</p>
<p>## Workarounds</p>
<p>- Restrict network access to the HTTP endpoint (firewall / reverse proxy / VPN) so only trusted callers can reach it.
- Run in stdio mode, which has no multi-tenant HTTP surface.
- If default-scope backups from a prior single-tenant deployment are not needed, removing them eliminates the exposure.</p>
<p>## Credit</p>
<p>Reported by @DavidCarliez.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-n8n-mcp-cve-2026-55608"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-55608</id>
    <title>CVE-2026-55608 — n8n-MCP: Incorrect authorization can expose default-scope workflow version backups in multi-tenant HTTP mode</title>
    <updated>2026-10-05T09:36:28.262617+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> czlonkowski n8n-mcp</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-55608"/>
  </entry>
</feed>
