<?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 20:33:51 +0000</lastBuildDate>
    <item>
      <title>CLEANSTART-2026-WK22081 — Security fix for ghsa-mwf2-3pr3-8698 applied in: n8n 2.28.0-r2</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-wk22081</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: n8n&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the n8n package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: n8n&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the n8n package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-wk22081</guid>
    </item>
    <item>
      <title>CVE-2026-67318 — axios 1.13.0 before 1.18.0 maxBodyLength Bypass via HTTP/2</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-67318</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; axios&lt;/p&gt;
&lt;p&gt;axios versions &amp;gt;=1.13.0 (Node.js HTTP adapter) fail to enforce the configured maxBodyLength limit on streamed request bodies when requests are sent with httpVersion: 2. Because Node&amp;#39;s HTTP/2 request API does not honor the maxBodyLength option and axios&amp;#39;s byte-counting stream wrapper is gated on maxRedirects === 0, an attacker who controls a stream passed to axios can cause the application to transmit outbound data exceeding the configured finite maxBodyLength. Impact is limited to resource consumption and policy bypass (excess egress, upstream quota consumption, limited availability); it does not enable code execution, credential disclosure, or request-destination control. Calls using the default maxBodyLength: -1 and browser adapters are not affected.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; axios&lt;/p&gt;
&lt;p&gt;axios versions &amp;gt;=1.13.0 (Node.js HTTP adapter) fail to enforce the configured maxBodyLength limit on streamed request bodies when requests are sent with httpVersion: 2. Because Node&amp;#39;s HTTP/2 request API does not honor the maxBodyLength option and axios&amp;#39;s byte-counting stream wrapper is gated on maxRedirects === 0, an attacker who controls a stream passed to axios can cause the application to transmit outbound data exceeding the configured finite maxBodyLength. Impact is limited to resource consumption and policy bypass (excess egress, upstream quota consumption, limited availability); it does not enable code execution, credential disclosure, or request-destination control. Calls using the default maxBodyLength: -1 and browser adapters are not affected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-67318</guid>
    </item>
  </channel>
</rss>
