<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-14T08:37:35.364850+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/brew-n8n-mcp-cve-2026-45582</id>
    <title>BREW-n8n-mcp-CVE-2026-45582 — n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters</title>
    <updated>2026-10-14T08:37:35.366986+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 affected versions of n8n-mcp, the workflow telemetry sanitizer could retain partial fragments of URL-shaped node parameters before sending workflow data to the project's anonymous telemetry backend. Values placed in HTTP-Request-style node parameters — such as customer or tenant identifiers, short secrets embedded in query strings, and signed request parameters — could therefore appear in stored telemetry, contrary to the collection boundary documented in `PRIVACY.md`.</p>
<p>## Impact</p>
<p>Operators with access to the project's telemetry backend could read partial fragments of workflow URL parameters that should not have been collected. The bug was scoped to URL-shaped fields in workflow *definitions*; credentials, OAuth tokens, and workflow *execution* data are not affected — credentials are removed by a separate code path, and long secrets and known-provider tokens are matched by dedicated patterns.</p>
<p>## Patches</p>
<p>Fixed in **n8n-mcp `2.51.3`**. Upgrading is the recommended remediation.</p>
<p>## Workarounds</p>
<p>For users who cannot upgrade immediately, disable anonymous telemetry by setting any of these environment variables to `true`:</p>
<p>- `N8N_MCP_TELEMETRY_DISABLED`
- `TELEMETRY_DISABLED`
- `DISABLE_TELEMETRY`</p>
<p>## Credit</p>
<p>Reported by @u-ktdi.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/brew-n8n-mcp-cve-2026-45582"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-45582</id>
    <title>CVE-2026-45582 — n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters</title>
    <updated>2026-10-14T08:37:35.367085+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.51.3, the workflow telemetry sanitizer could retain partial fragments of URL-shaped node parameters before sending workflow data to the project's anonymous telemetry backend. Values placed in HTTP-Request-style node parameters — such as customer or tenant identifiers, short secrets embedded in query strings, and signed request parameters — could therefore appear in stored telemetry, contrary to the collection boundary documented in PRIVACY.md. This vulnerability is fixed in 2.51.3.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-45582"/>
  </entry>
</feed>
