<?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>Sun, 04 Oct 2026 09:22:29 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-329275</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329275</link>
      <description>EUVD-2026-329275</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329275</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54309</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54309</link>
      <description>&lt;p&gt;n8n is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, when @n8n/mcp-browser is run in HTTP transport mode, the MCP endpoint accepts session initialization and tool invocation requests without any authentication. Any network-reachable client, or any website visited by the user, can establish an MCP session and invoke browser-control tools. Where the n8n AI Browser Bridge extension is installed and a browser connection is active, an unauthenticated caller can access browser-control capabilities including navigation, JavaScript evaluation, and cookie and storage access against the user&amp;#39;s real browser profile. This issue only affects instances where @n8n/mcp-browser is run with the HTTP transport (--transport http). This vulnerability is fixed in 2.25.7 and 2.26.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;n8n is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, when @n8n/mcp-browser is run in HTTP transport mode, the MCP endpoint accepts session initialization and tool invocation requests without any authentication. Any network-reachable client, or any website visited by the user, can establish an MCP session and invoke browser-control tools. Where the n8n AI Browser Bridge extension is installed and a browser connection is active, an unauthenticated caller can access browser-control capabilities including navigation, JavaScript evaluation, and cookie and storage access against the user&amp;#39;s real browser profile. This issue only affects instances where @n8n/mcp-browser is run with the HTTP transport (--transport http). This vulnerability is fixed in 2.25.7 and 2.26.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54309</guid>
    </item>
    <item>
      <title>GHSA-qrx8-25qr-5r7v — n8n: MCP Browser HTTP Transport Exposes Unauthenticated Browser-Control Sessions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qrx8-25qr-5r7v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: n8n&lt;/p&gt;
&lt;p&gt;## Impact
When `@n8n/mcp-browser` is run in HTTP transport mode, the MCP endpoint accepts session initialization and tool invocation requests without any authentication. Any network-reachable client, or any website visited by the user, can establish an MCP session and invoke browser-control tools.&lt;/p&gt;
&lt;p&gt;Where the n8n AI Browser Bridge extension is installed and a browser connection is active, an unauthenticated caller can access browser-control capabilities including navigation, JavaScript evaluation, and cookie and storage access against the user&amp;#39;s real browser profile.&lt;/p&gt;
&lt;p&gt;This issue only affects instances where `@n8n/mcp-browser` is run with the HTTP transport (`--transport http`). The default transport is stdio, which is not affected.&lt;/p&gt;
&lt;p&gt;## Patches
The issue has been fixed in n8n versions 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later to remediate the vulnerability.&lt;/p&gt;
&lt;p&gt;## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Avoid running `@n8n/mcp-browser` with the HTTP transport; use the default stdio transport instead.
- If HTTP transport is required, restrict network access to the listening port to trusted clients only using host-based firewall rules.&lt;/p&gt;
&lt;p&gt;These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: n8n&lt;/p&gt;
&lt;p&gt;## Impact
When `@n8n/mcp-browser` is run in HTTP transport mode, the MCP endpoint accepts session initialization and tool invocation requests without any authentication. Any network-reachable client, or any website visited by the user, can establish an MCP session and invoke browser-control tools.&lt;/p&gt;
&lt;p&gt;Where the n8n AI Browser Bridge extension is installed and a browser connection is active, an unauthenticated caller can access browser-control capabilities including navigation, JavaScript evaluation, and cookie and storage access against the user&amp;#39;s real browser profile.&lt;/p&gt;
&lt;p&gt;This issue only affects instances where `@n8n/mcp-browser` is run with the HTTP transport (`--transport http`). The default transport is stdio, which is not affected.&lt;/p&gt;
&lt;p&gt;## Patches
The issue has been fixed in n8n versions 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later to remediate the vulnerability.&lt;/p&gt;
&lt;p&gt;## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Avoid running `@n8n/mcp-browser` with the HTTP transport; use the default stdio transport instead.
- If HTTP transport is required, restrict network access to the listening port to trusted clients only using host-based firewall rules.&lt;/p&gt;
&lt;p&gt;These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qrx8-25qr-5r7v</guid>
    </item>
    <item>
      <title>NCSC-2026-0212 — Kwetsbaarheden verholpen in n8n workflow automation platform</title>
      <link>https://cve.radiocsirt.org/vuln/ncsc-2026-0212</link>
      <description>NCSC-2026-0212</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ncsc-2026-0212</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1875 — n8n: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1875</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, SQL-Injection- und Cross-Site-Scripting-Angriffe durchzuführen, Daten zu manipulieren, einen Denial-of-Service-Zustand zu verursachen oder vertrauliche Informationen offenzulegen, was weitere Angriffe einschließlich einer Rechteausweitung ermöglichen kann.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, SQL-Injection- und Cross-Site-Scripting-Angriffe durchzuführen, Daten zu manipulieren, einen Denial-of-Service-Zustand zu verursachen oder vertrauliche Informationen offenzulegen, was weitere Angriffe einschließlich einer Rechteausweitung ermöglichen kann.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1875</guid>
    </item>
  </channel>
</rss>
