<?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>Sat, 03 Oct 2026 09:07:51 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-00784</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-00784</link>
      <description>bdu:2026-00784</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-00784</guid>
    </item>
    <item>
      <title>EUVD-2026-265565</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-265565</link>
      <description>EUVD-2026-265565</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-265565</guid>
    </item>
    <item>
      <title>fkie_cve-2025-68949</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-68949</link>
      <description>&lt;p&gt;n8n is an open source workflow automation platform. From 1.36.0 to before 2.2.0, the Webhook node’s IP whitelist validation performed partial string matching instead of exact IP comparison. As a result, an incoming request could be accepted if the source IP address merely contained the configured whitelist entry as a substring. This issue affected instances where workflow editors relied on IP-based access controls to restrict webhook access. Both IPv4 and IPv6 addresses were impacted. An attacker with a non-whitelisted IP could bypass restrictions if their IP shared a partial prefix with a trusted address, undermining the intended security boundary. This vulnerability is fixed in 2.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;n8n is an open source workflow automation platform. From 1.36.0 to before 2.2.0, the Webhook node’s IP whitelist validation performed partial string matching instead of exact IP comparison. As a result, an incoming request could be accepted if the source IP address merely contained the configured whitelist entry as a substring. This issue affected instances where workflow editors relied on IP-based access controls to restrict webhook access. Both IPv4 and IPv6 addresses were impacted. An attacker with a non-whitelisted IP could bypass restrictions if their IP shared a partial prefix with a trusted address, undermining the intended security boundary. This vulnerability is fixed in 2.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-68949</guid>
    </item>
    <item>
      <title>GHSA-w96v-gf22-crwp — n8n: Webhook Node IP Whitelist Bypass via Partial String Matching</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w96v-gf22-crwp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: n8n&lt;/p&gt;
&lt;p&gt;## Impact
The Webhook node’s IP whitelist validation performed partial string matching instead of exact IP comparison. As a result, an incoming request could be accepted if the source IP address merely contained the configured whitelist entry as a substring.&lt;/p&gt;
&lt;p&gt;This issue affected instances where workflow editors relied on IP-based access controls to restrict webhook access. Both IPv4 and IPv6 addresses were impacted. An attacker with a non-whitelisted IP could bypass restrictions if their IP shared a partial prefix with a trusted address, undermining the intended security boundary.&lt;/p&gt;
&lt;p&gt;## Patches
This issue has been patched in version 2.2.0.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to v2.2.0 or later, where IP whitelist validation uses strict IP comparison logic rather than partial string matching.&lt;/p&gt;
&lt;p&gt;## Workarounds
Users unable to upgrade immediately should avoid relying solely on IP whitelisting for webhook security. Recommended mitigations include:
- Adding authentication mechanisms such as shared secrets, HMAC signatures, or API keys.
- Avoiding short or prefix-based whitelist entries.
- Enforcing IP filtering at the network layer (for example, via reverse proxies or firewalls).&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 Webhook node’s IP whitelist validation performed partial string matching instead of exact IP comparison. As a result, an incoming request could be accepted if the source IP address merely contained the configured whitelist entry as a substring.&lt;/p&gt;
&lt;p&gt;This issue affected instances where workflow editors relied on IP-based access controls to restrict webhook access. Both IPv4 and IPv6 addresses were impacted. An attacker with a non-whitelisted IP could bypass restrictions if their IP shared a partial prefix with a trusted address, undermining the intended security boundary.&lt;/p&gt;
&lt;p&gt;## Patches
This issue has been patched in version 2.2.0.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to v2.2.0 or later, where IP whitelist validation uses strict IP comparison logic rather than partial string matching.&lt;/p&gt;
&lt;p&gt;## Workarounds
Users unable to upgrade immediately should avoid relying solely on IP whitelisting for webhook security. Recommended mitigations include:
- Adding authentication mechanisms such as shared secrets, HMAC signatures, or API keys.
- Avoiding short or prefix-based whitelist entries.
- Enforcing IP filtering at the network layer (for example, via reverse proxies or firewalls).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w96v-gf22-crwp</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0097 — n8n: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0097</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in n8n ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in n8n ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0097</guid>
    </item>
  </channel>
</rss>
