<?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>Mon, 05 Oct 2026 02:43:16 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-335264</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-335264</link>
      <description>EUVD-2026-335264</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-335264</guid>
    </item>
    <item>
      <title>fkie_cve-2026-59257</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-59257</link>
      <description>&lt;p&gt;n8n before 1.123.61, 2.x before 2.27.4, and 2.28.x before 2.28.1 contains a SQL injection vulnerability in the legacy MySQL v1 node&amp;#39;s executeQuery operation. The operation substitutes evaluated {{ ... }} expression values directly into the raw SQL string without parameterization. When a workflow uses this operation with expression-sourced values and is connected to an externally-reachable trigger (such as a Webhook node), attacker-controlled input reaching those expressions results in SQL injection, allowing execution of arbitrary SQL with the configured MySQL credentials&amp;#39; privileges. The MySQL v2 node, which uses parameterized queries, is not affected.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;n8n before 1.123.61, 2.x before 2.27.4, and 2.28.x before 2.28.1 contains a SQL injection vulnerability in the legacy MySQL v1 node&amp;#39;s executeQuery operation. The operation substitutes evaluated {{ ... }} expression values directly into the raw SQL string without parameterization. When a workflow uses this operation with expression-sourced values and is connected to an externally-reachable trigger (such as a Webhook node), attacker-controlled input reaching those expressions results in SQL injection, allowing execution of arbitrary SQL with the configured MySQL credentials&amp;#39; privileges. The MySQL v2 node, which uses parameterized queries, is not affected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-59257</guid>
    </item>
    <item>
      <title>GHSA-hwmj-qg4v-cvg9 — n8n: MySQL v1 Node executeQuery Operation Allows SQL Injection via Unparameterized Expression Interpolation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hwmj-qg4v-cvg9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: n8n&lt;/p&gt;
&lt;p&gt;## Impact
The legacy MySQL v1 node&amp;#39;s `executeQuery` operation substitutes evaluated `{{ ... }}` expression values directly into the raw SQL string without parameterization. If a workflow uses this operation with expression-sourced values in the query and is connected to an externally-reachable trigger (such as a Webhook node), attacker-controlled input reaching those expressions results in SQL injection.&lt;/p&gt;
&lt;p&gt;Successful exploitation allows arbitrary SQL execution with the configured MySQL credentials&amp;#39; privileges, enabling unauthorized disclosure, modification, or deletion of data in the downstream database. MySQL v2 node is not affected.&lt;/p&gt;
&lt;p&gt;This issue can affect only instances running workflows that use the MySQL v1 node with `executeQuery` operations.&lt;/p&gt;
&lt;p&gt;## Patches
The issue has been fixed in n8n versions 1.123.61, 2.27.4, and 2.28.1. 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:
- Disable the MySQL node by adding `n8n-nodes-base.mySql` to the `NODES_EXCLUDE` environment variable, or audit and restrict access to workflows using the MySQL v1 node with the `executeQuery` operation.
- Ensure that webhook endpoints used in workflows containing MySQL v1 `executeQuery` nodes with expression interpolation require authentication.
- Migrate affected workflows to use the MySQL v2 node, which uses parameterized queries.&lt;/p&gt;
&lt;p&gt;These w…&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
The legacy MySQL v1 node&amp;#39;s `executeQuery` operation substitutes evaluated `{{ ... }}` expression values directly into the raw SQL string without parameterization. If a workflow uses this operation with expression-sourced values in the query and is connected to an externally-reachable trigger (such as a Webhook node), attacker-controlled input reaching those expressions results in SQL injection.&lt;/p&gt;
&lt;p&gt;Successful exploitation allows arbitrary SQL execution with the configured MySQL credentials&amp;#39; privileges, enabling unauthorized disclosure, modification, or deletion of data in the downstream database. MySQL v2 node is not affected.&lt;/p&gt;
&lt;p&gt;This issue can affect only instances running workflows that use the MySQL v1 node with `executeQuery` operations.&lt;/p&gt;
&lt;p&gt;## Patches
The issue has been fixed in n8n versions 1.123.61, 2.27.4, and 2.28.1. 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:
- Disable the MySQL node by adding `n8n-nodes-base.mySql` to the `NODES_EXCLUDE` environment variable, or audit and restrict access to workflows using the MySQL v1 node with the `executeQuery` operation.
- Ensure that webhook endpoints used in workflows containing MySQL v1 `executeQuery` nodes with expression interpolation require authentication.
- Migrate affected workflows to use the MySQL v2 node, which uses parameterized queries.&lt;/p&gt;
&lt;p&gt;These w…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hwmj-qg4v-cvg9</guid>
    </item>
    <item>
      <title>NCSC-2026-0228 — Kwetsbaarheden verholpen in n8n workflow automation platform</title>
      <link>https://cve.radiocsirt.org/vuln/ncsc-2026-0228</link>
      <description>NCSC-2026-0228</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ncsc-2026-0228</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2067 — n8n: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2067</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um SQL-Injection durchzuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um SQL-Injection durchzuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2067</guid>
    </item>
  </channel>
</rss>
