<?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 10:13:01 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-329827</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329827</link>
      <description>EUVD-2026-329827</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329827</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54308</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54308</link>
      <description>&lt;p&gt;n8n is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, the MicrosoftAgent365Trigger and StripeTrigger node did not validate that inbound requests. As a result, an unauthenticated attacker who knows the webhook URL could submit a forged payload and cause the workflow to execute with attacker-controlled data. 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, the MicrosoftAgent365Trigger and StripeTrigger node did not validate that inbound requests. As a result, an unauthenticated attacker who knows the webhook URL could submit a forged payload and cause the workflow to execute with attacker-controlled data. 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-54308</guid>
    </item>
    <item>
      <title>GHSA-jvc7-762p-3743 — n8n: Missing Token Validation on Microsoft Agent 365 Trigger and Stripe Nodes</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jvc7-762p-3743</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: n8n&lt;/p&gt;
&lt;p&gt;## Impact
The `MicrosoftAgent365Trigger` and `StripeTrigger` node did not validate that inbound requests. As a result, an unauthenticated attacker who knows the webhook URL could submit a forged payload and cause the workflow to execute with attacker-controlled data.&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:
- Deactivate any workflows using the Microsoft Agent 365 Trigger node or Stripe Trigger node until the instance can be upgraded.
- Restrict network access to the n8n webhook endpoint to trusted sources only.&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
The `MicrosoftAgent365Trigger` and `StripeTrigger` node did not validate that inbound requests. As a result, an unauthenticated attacker who knows the webhook URL could submit a forged payload and cause the workflow to execute with attacker-controlled data.&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:
- Deactivate any workflows using the Microsoft Agent 365 Trigger node or Stripe Trigger node until the instance can be upgraded.
- Restrict network access to the n8n webhook endpoint to trusted sources only.&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-jvc7-762p-3743</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>
