<?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>Fri, 02 Oct 2026 10:03:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-35948 — CRLF Injection in Nodejs ‘undici’ via Content-Type</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-35948</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nodejs undici&lt;/p&gt;
&lt;p&gt;undici is an HTTP/1.1 client, written from scratch for Node.js.`=&amp;lt; undici@5.8.0` users are vulnerable to _CRLF Injection_ on headers when using unsanitized input as request headers, more specifically, inside the `content-type` header. Example: ``` import { request } from &amp;#39;undici&amp;#39; const unsanitizedContentTypeInput = &amp;#39;application/json\r\n\r\nGET /foo2 HTTP/1.1&amp;#39; await request(&amp;#39;http://localhost:3000, { method: &amp;#39;GET&amp;#39;, headers: { &amp;#39;content-type&amp;#39;: unsanitizedContentTypeInput }, }) ``` The above snippet will perform two requests in a single `request` API call: 1) `http://localhost:3000/` 2) `http://localhost:3000/foo2` This issue was patched in Undici v5.8.1. Sanitize input when sending content-type headers using user input as a workaround.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nodejs undici&lt;/p&gt;
&lt;p&gt;undici is an HTTP/1.1 client, written from scratch for Node.js.`=&amp;lt; undici@5.8.0` users are vulnerable to _CRLF Injection_ on headers when using unsanitized input as request headers, more specifically, inside the `content-type` header. Example: ``` import { request } from &amp;#39;undici&amp;#39; const unsanitizedContentTypeInput = &amp;#39;application/json\r\n\r\nGET /foo2 HTTP/1.1&amp;#39; await request(&amp;#39;http://localhost:3000, { method: &amp;#39;GET&amp;#39;, headers: { &amp;#39;content-type&amp;#39;: unsanitizedContentTypeInput }, }) ``` The above snippet will perform two requests in a single `request` API call: 1) `http://localhost:3000/` 2) `http://localhost:3000/foo2` This issue was patched in Undici v5.8.1. Sanitize input when sending content-type headers using user input as a workaround.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-35948</guid>
    </item>
  </channel>
</rss>
