<?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 17:17:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-329245</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329245</link>
      <description>EUVD-2026-329245</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329245</guid>
    </item>
    <item>
      <title>fkie_cve-2026-56357</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-56357</link>
      <description>&lt;p&gt;n8n before 1.123.15 and 2.5.0 contains a webhook forgery vulnerability in the GitHub Webhook Trigger node that fails to implement HMAC-SHA256 signature verification. Attackers who know the webhook URL can send unsigned POST requests to trigger workflows with arbitrary data, spoofing GitHub webhook events.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;n8n before 1.123.15 and 2.5.0 contains a webhook forgery vulnerability in the GitHub Webhook Trigger node that fails to implement HMAC-SHA256 signature verification. Attackers who know the webhook URL can send unsigned POST requests to trigger workflows with arbitrary data, spoofing GitHub webhook events.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-56357</guid>
    </item>
    <item>
      <title>GHSA-mqpr-49jj-32rc — n8n: Webhook Forgery on Github Webhook Trigger</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mqpr-49jj-32rc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: n8n&lt;/p&gt;
&lt;p&gt;## Impact
An attacker who knows the webhook URL of a workflow using the GitHub Webhook Trigger node could send unsigned POST requests and trigger the workflow with arbitrary data. The node did not implement the HMAC-SHA256 signature verification that GitHub provides to authenticate webhook deliveries, allowing any party to spoof GitHub webhook events.&lt;/p&gt;
&lt;p&gt;## Patches
The issue has been fixed in n8n versions 2.5.0 and 1.123.15. 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:
- Limit workflow creation and editing permissions to fully trusted users only.
- Restrict network access to the n8n webhook endpoint to known GitHub webhook IP ranges.&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
An attacker who knows the webhook URL of a workflow using the GitHub Webhook Trigger node could send unsigned POST requests and trigger the workflow with arbitrary data. The node did not implement the HMAC-SHA256 signature verification that GitHub provides to authenticate webhook deliveries, allowing any party to spoof GitHub webhook events.&lt;/p&gt;
&lt;p&gt;## Patches
The issue has been fixed in n8n versions 2.5.0 and 1.123.15. 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:
- Limit workflow creation and editing permissions to fully trusted users only.
- Restrict network access to the n8n webhook endpoint to known GitHub webhook IP ranges.&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-mqpr-49jj-32rc</guid>
    </item>
    <item>
      <title>NCSC-2026-0248 — Kwetsbaarheden verholpen in n8n workflow automation platform</title>
      <link>https://cve.radiocsirt.org/vuln/ncsc-2026-0248</link>
      <description>NCSC-2026-0248</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ncsc-2026-0248</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0532 — n8n: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0532</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, um Daten zu manipulieren, um einen SQL-Injection Angriff durchzuführen, und um einen Cross-Site Scripting Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, um Daten zu manipulieren, um einen SQL-Injection Angriff durchzuführen, und um einen Cross-Site Scripting Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0532</guid>
    </item>
  </channel>
</rss>
