<?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 22:42:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-44974 — Parameter smuggling in @hapi/content header parser allows upload-filter bypass via duplicate parameters</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-44974</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; hapijs content&lt;/p&gt;
&lt;p&gt;@hapi/content provided HTTP Content-* headers parsing. Prior to 6.0.2, Content.disposition() retained the last occurrence of each duplicate parameter while Content.type() retained the first occurrence of duplicate charset and boundary parameters, creating a parameter-smuggling primitive when another component in the request-processing chain resolves duplicates the opposite way. This can allow an upload filename allowlist bypass in headers such as Content-Disposition: form-data; name=&amp;#34;file&amp;#34;; filename=&amp;#34;safe.txt&amp;#34;; filename=&amp;#34;shell.php&amp;#34;. This issue is fixed in version 6.0.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; hapijs content&lt;/p&gt;
&lt;p&gt;@hapi/content provided HTTP Content-* headers parsing. Prior to 6.0.2, Content.disposition() retained the last occurrence of each duplicate parameter while Content.type() retained the first occurrence of duplicate charset and boundary parameters, creating a parameter-smuggling primitive when another component in the request-processing chain resolves duplicates the opposite way. This can allow an upload filename allowlist bypass in headers such as Content-Disposition: form-data; name=&amp;#34;file&amp;#34;; filename=&amp;#34;safe.txt&amp;#34;; filename=&amp;#34;shell.php&amp;#34;. This issue is fixed in version 6.0.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-44974</guid>
    </item>
  </channel>
</rss>
