<?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>Thu, 08 Oct 2026 18:50:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43966 — HTTP Response Splitting via Non-VCHAR Bytes in cow_http_struct_hd:escape_string/2</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-43966</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ninenines cowlib&lt;/p&gt;
&lt;p&gt;Improper Neutralization of CRLF Sequences in HTTP Headers (&amp;#39;HTTP Request/Response Splitting&amp;#39;) vulnerability in ninenines cowlib allows HTTP response splitting via non-VCHAR bytes in structured-fields string values.&lt;/p&gt;
&lt;p&gt;cow_http_struct_hd:escape_string/2 in cowlib only escapes \ and &amp;#34;, passing all other bytes through verbatim. This creates an encoder/decoder asymmetry: the matching parser accepts only printable ASCII (0x20–0x7E, excluding &amp;#34; and \), but the encoder emits any byte including CR and LF. An application that builds a structured HTTP header via cow_http_struct_hd:item/1 (or a higher-level wrapper such as cow_http_hd:wt_protocol/1) from attacker-controlled input can have \r\n injected into the serialized header value. Once on the wire, the injected CRLF terminates the current header and any following bytes are interpreted as a new header, enabling HTTP response splitting.&lt;/p&gt;
&lt;p&gt;This issue affects cowlib from 2.9.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ninenines cowlib&lt;/p&gt;
&lt;p&gt;Improper Neutralization of CRLF Sequences in HTTP Headers (&amp;#39;HTTP Request/Response Splitting&amp;#39;) vulnerability in ninenines cowlib allows HTTP response splitting via non-VCHAR bytes in structured-fields string values.&lt;/p&gt;
&lt;p&gt;cow_http_struct_hd:escape_string/2 in cowlib only escapes \ and &amp;#34;, passing all other bytes through verbatim. This creates an encoder/decoder asymmetry: the matching parser accepts only printable ASCII (0x20–0x7E, excluding &amp;#34; and \), but the encoder emits any byte including CR and LF. An application that builds a structured HTTP header via cow_http_struct_hd:item/1 (or a higher-level wrapper such as cow_http_hd:wt_protocol/1) from attacker-controlled input can have \r\n injected into the serialized header value. Once on the wire, the injected CRLF terminates the current header and any following bytes are interpreted as a new header, enabling HTTP response splitting.&lt;/p&gt;
&lt;p&gt;This issue affects cowlib from 2.9.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-43966</guid>
    </item>
  </channel>
</rss>
