<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 16:08:43 +0000</lastBuildDate>
    <item>
      <title>BREW-n8n-mcp-CVE-2026-45582 — n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters</title>
      <link>https://cve.radiocsirt.org/vuln/brew-n8n-mcp-cve-2026-45582</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: n8n-mcp&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;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`.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Operators with access to the project&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in **n8n-mcp `2.51.3`**. Upgrading is the recommended remediation.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;For users who cannot upgrade immediately, disable anonymous telemetry by setting any of these environment variables to `true`:&lt;/p&gt;
&lt;p&gt;- `N8N_MCP_TELEMETRY_DISABLED`
- `TELEMETRY_DISABLED`
- `DISABLE_TELEMETRY`&lt;/p&gt;
&lt;p&gt;## Credit&lt;/p&gt;
&lt;p&gt;Reported by @u-ktdi.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: n8n-mcp&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;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`.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Operators with access to the project&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in **n8n-mcp `2.51.3`**. Upgrading is the recommended remediation.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;For users who cannot upgrade immediately, disable anonymous telemetry by setting any of these environment variables to `true`:&lt;/p&gt;
&lt;p&gt;- `N8N_MCP_TELEMETRY_DISABLED`
- `TELEMETRY_DISABLED`
- `DISABLE_TELEMETRY`&lt;/p&gt;
&lt;p&gt;## Credit&lt;/p&gt;
&lt;p&gt;Reported by @u-ktdi.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-n8n-mcp-cve-2026-45582</guid>
    </item>
    <item>
      <title>EUVD-2026-322944</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-322944</link>
      <description>EUVD-2026-322944</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-322944</guid>
    </item>
    <item>
      <title>fkie_cve-2026-45582</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45582</link>
      <description>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-45582</guid>
    </item>
    <item>
      <title>GHSA-f3rg-xqjj-cj9w — n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f3rg-xqjj-cj9w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: n8n-mcp&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;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`.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Operators with access to the project&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in **n8n-mcp `2.51.3`**. Upgrading is the recommended remediation.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;For users who cannot upgrade immediately, disable anonymous telemetry by setting any of these environment variables to `true`:&lt;/p&gt;
&lt;p&gt;- `N8N_MCP_TELEMETRY_DISABLED`
- `TELEMETRY_DISABLED`
- `DISABLE_TELEMETRY`&lt;/p&gt;
&lt;p&gt;## Credit&lt;/p&gt;
&lt;p&gt;Reported by @u-ktdi.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: n8n-mcp&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;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`.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Operators with access to the project&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in **n8n-mcp `2.51.3`**. Upgrading is the recommended remediation.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;For users who cannot upgrade immediately, disable anonymous telemetry by setting any of these environment variables to `true`:&lt;/p&gt;
&lt;p&gt;- `N8N_MCP_TELEMETRY_DISABLED`
- `TELEMETRY_DISABLED`
- `DISABLE_TELEMETRY`&lt;/p&gt;
&lt;p&gt;## Credit&lt;/p&gt;
&lt;p&gt;Reported by @u-ktdi.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f3rg-xqjj-cj9w</guid>
    </item>
  </channel>
</rss>
