<?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>Mon, 16 Nov 2026 22:31:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-404322</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-404322</link>
      <description>EUVD-2026-404322</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-404322</guid>
    </item>
    <item>
      <title>fkie_cve-2026-125333</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-125333</link>
      <description>&lt;p&gt;Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. From 0.1.2 until 1.4.3, forge.http uses _trimString() in lib/http.js to remove trailing whitespace from response header values and cookie names and values with a regular expression that can take quadratic time. A malicious server or on-path attacker can supply a long whitespace run followed by a non-whitespace character in a response header, causing response.readHeader() or response.getCookies() to repeatedly scan the input and block the Node.js event loop or browser tab for minutes. Applications are affected only when they use forge.http with a socket pool to communicate with an untrusted server; forge.http is not loaded by require(&amp;#39;node-forge&amp;#39;), and the issue has no confidentiality or integrity impact. This issue is fixed in version 1.4.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. From 0.1.2 until 1.4.3, forge.http uses _trimString() in lib/http.js to remove trailing whitespace from response header values and cookie names and values with a regular expression that can take quadratic time. A malicious server or on-path attacker can supply a long whitespace run followed by a non-whitespace character in a response header, causing response.readHeader() or response.getCookies() to repeatedly scan the input and block the Node.js event loop or browser tab for minutes. Applications are affected only when they use forge.http with a socket pool to communicate with an untrusted server; forge.http is not loaded by require(&amp;#39;node-forge&amp;#39;), and the issue has no confidentiality or integrity impact. This issue is fixed in version 1.4.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-125333</guid>
    </item>
    <item>
      <title>GHSA-6cv4-p8m7-4r25 — Forge: ReDoS in forge.http response header and cookie trimming</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6cv4-p8m7-4r25</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-forge&lt;/p&gt;
&lt;p&gt;`forge.http` trims response header and `Set-Cookie` values with the regular expression `/\s*$/`, which takes quadratic time on a long run of whitespace followed by another character. A server or on-path attacker can block a `forge.http` client for minutes with one large response header. Fixed in node-forge 1.4.3.&lt;/p&gt;
&lt;p&gt;### Details
`_trimString()` in `lib/http.js` removes trailing whitespace with `str.replace(/\s*$/, &amp;#39;&amp;#39;)`. On a string of n whitespace characters followed by a non-whitespace character, the regular expression engine tries a match at each of the n positions and scans the rest of the run each time, so the work is O(n^2). `forge.http` calls `_trimString()` on every response header value read by `response.readHeader()`, and again on cookie names and values in `response.getCookies()`. There is no limit on header size.&lt;/p&gt;
&lt;p&gt;With Node.js 24, an 80 KB header value takes about 4 seconds to parse, and 1 MB about 10 minutes, during which the event loop (or browser tab) is blocked.&lt;/p&gt;
&lt;p&gt;`forge.http` is not loaded by `require(&amp;#39;node-forge&amp;#39;)`. It is part of the `forge.all` bundle and needs a socket pool provided by the application (historically Flash sockets via `forge.xhr`), so few applications use it.&lt;/p&gt;
&lt;p&gt;The fix trims trailing whitespace with a loop, as `lib/pem.js` has done since 1.4.1. The trimmed result is unchanged.&lt;/p&gt;
&lt;p&gt;#### Patches
Fixed in node-forge 1.4.3.&lt;/p&gt;
&lt;p&gt;#### Workarounds
Limit the size of HTTP response headers before passing them to `forge.http`, for example in the socket pool&amp;#39;s dat…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-forge&lt;/p&gt;
&lt;p&gt;`forge.http` trims response header and `Set-Cookie` values with the regular expression `/\s*$/`, which takes quadratic time on a long run of whitespace followed by another character. A server or on-path attacker can block a `forge.http` client for minutes with one large response header. Fixed in node-forge 1.4.3.&lt;/p&gt;
&lt;p&gt;### Details
`_trimString()` in `lib/http.js` removes trailing whitespace with `str.replace(/\s*$/, &amp;#39;&amp;#39;)`. On a string of n whitespace characters followed by a non-whitespace character, the regular expression engine tries a match at each of the n positions and scans the rest of the run each time, so the work is O(n^2). `forge.http` calls `_trimString()` on every response header value read by `response.readHeader()`, and again on cookie names and values in `response.getCookies()`. There is no limit on header size.&lt;/p&gt;
&lt;p&gt;With Node.js 24, an 80 KB header value takes about 4 seconds to parse, and 1 MB about 10 minutes, during which the event loop (or browser tab) is blocked.&lt;/p&gt;
&lt;p&gt;`forge.http` is not loaded by `require(&amp;#39;node-forge&amp;#39;)`. It is part of the `forge.all` bundle and needs a socket pool provided by the application (historically Flash sockets via `forge.xhr`), so few applications use it.&lt;/p&gt;
&lt;p&gt;The fix trims trailing whitespace with a loop, as `lib/pem.js` has done since 1.4.1. The trimmed result is unchanged.&lt;/p&gt;
&lt;p&gt;#### Patches
Fixed in node-forge 1.4.3.&lt;/p&gt;
&lt;p&gt;#### Workarounds
Limit the size of HTTP response headers before passing them to `forge.http`, for example in the socket pool&amp;#39;s dat…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6cv4-p8m7-4r25</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-125333 — Forge: ReDoS in forge.http response header and cookie trimming</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-125333</link>
      <description>msrc_CVE-2026-125333</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-125333</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-125333</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-125333</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: node-node-forge, Ubuntu:22.04:LTS: node-node-forge&lt;/p&gt;
&lt;p&gt;Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. From 0.1.2 until 1.4.3, forge.http uses _trimString() in lib/http.js to remove trailing whitespace from response header values and cookie names and values with a regular expression that can take quadratic time. A malicious server or on-path attacker can supply a long whitespace run followed by a non-whitespace character in a response header, causing response.readHeader() or response.getCookies() to repeatedly scan the input and block the Node.js event loop or browser tab for minutes. Applications are affected only when they use forge.http with a socket pool to communicate with an untrusted server; forge.http is not loaded by require(&amp;#39;node-forge&amp;#39;), and the issue has no confidentiality or integrity impact. This issue is fixed in version 1.4.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: node-node-forge, Ubuntu:22.04:LTS: node-node-forge&lt;/p&gt;
&lt;p&gt;Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. From 0.1.2 until 1.4.3, forge.http uses _trimString() in lib/http.js to remove trailing whitespace from response header values and cookie names and values with a regular expression that can take quadratic time. A malicious server or on-path attacker can supply a long whitespace run followed by a non-whitespace character in a response header, causing response.readHeader() or response.getCookies() to repeatedly scan the input and block the Node.js event loop or browser tab for minutes. Applications are affected only when they use forge.http with a socket pool to communicate with an untrusted server; forge.http is not loaded by require(&amp;#39;node-forge&amp;#39;), and the issue has no confidentiality or integrity impact. This issue is fixed in version 1.4.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-125333</guid>
    </item>
  </channel>
</rss>
