<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T21:58:07.560915+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-329245</id>
    <title>EUVD-2026-329245</title>
    <updated>2026-10-06T21:58:07.626798+00:00</updated>
    <content>EUVD-2026-329245</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-329245"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-56357</id>
    <title>fkie_cve-2026-56357</title>
    <updated>2026-10-06T21:58:07.626837+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-56357"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-mqpr-49jj-32rc</id>
    <title>GHSA-mqpr-49jj-32rc — n8n: Webhook Forgery on Github Webhook Trigger</title>
    <updated>2026-10-06T21:58:07.626872+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: n8n</p>
<p>## 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.</p>
<p>## 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.</p>
<p>## 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.</p>
<p>These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-mqpr-49jj-32rc"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ncsc-2026-0248</id>
    <title>NCSC-2026-0248 — Kwetsbaarheden verholpen in n8n workflow automation platform</title>
    <updated>2026-10-06T21:58:07.626907+00:00</updated>
    <content>NCSC-2026-0248</content>
    <link href="https://cve.radiocsirt.org/vuln/ncsc-2026-0248"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0532</id>
    <title>WID-SEC-W-2026-0532 — n8n: Mehrere Schwachstellen</title>
    <updated>2026-10-06T21:58:07.626941+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0532"/>
  </entry>
</feed>
