<?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 21:26:34 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-17367</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-17367</link>
      <description>bdu:2026-17367</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-17367</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1385 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1385</link>
      <description>certfr-2026-avi-1385</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1385</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-YF34082 — follow-redirects is a Node</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-yf34082</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: qdrant, CleanStart: langfuse, CleanStart: langfuse-worker&lt;/p&gt;
&lt;p&gt;CVE-2026-111756 affects multiple packages. follow-redirects is a Node. See references for individual vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: qdrant, CleanStart: langfuse, CleanStart: langfuse-worker&lt;/p&gt;
&lt;p&gt;CVE-2026-111756 affects multiple packages. follow-redirects is a Node. See references for individual vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-yf34082</guid>
    </item>
    <item>
      <title>EUVD-2026-391384</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391384</link>
      <description>EUVD-2026-391384</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391384</guid>
    </item>
    <item>
      <title>fkie_cve-2026-111756</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-111756</link>
      <description>&lt;p&gt;follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From version 1.16.0 to before version 1.16.1, follow-redirects removes sensitive credential headers (Authorization, Proxy-Authorization, Cookie, and any caller-declared sensitiveHeaders) before following a redirect that crosses to a different host or downgrades to a less secure protocol. The removal routine iterates the caller&amp;#39;s headers container with for...in and matches header names against a filter. This assumes the headers container is a plain object keyed by header names. Node&amp;#39;s underlying http.request, which follow-redirects is a drop-in replacement for, also accepts headers as an alternating array of names and values. For an array, for...in yields the numeric indices &amp;#34;0&amp;#34;, &amp;#34;1&amp;#34;, &amp;#34;2&amp;#34; and so on, which never match a header-name filter, so nothing is removed. An application that sends array-form headers and follows an attacker-controlled cross-origin redirect therefore forwards its Authorization, Cookie, and Proxy-Authorization headers verbatim to the attacker-controlled destination, with no error or warning. The sensitiveHeaders option added to fix CVE-2026-40895 / GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the same helper. This is an unauthenticated confidentiality vulnerability: any remote server the victim application contacts can harvest the victim&amp;#39;s credential headers by responding with a cross-origin redirect. This issue has been patched in version…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From version 1.16.0 to before version 1.16.1, follow-redirects removes sensitive credential headers (Authorization, Proxy-Authorization, Cookie, and any caller-declared sensitiveHeaders) before following a redirect that crosses to a different host or downgrades to a less secure protocol. The removal routine iterates the caller&amp;#39;s headers container with for...in and matches header names against a filter. This assumes the headers container is a plain object keyed by header names. Node&amp;#39;s underlying http.request, which follow-redirects is a drop-in replacement for, also accepts headers as an alternating array of names and values. For an array, for...in yields the numeric indices &amp;#34;0&amp;#34;, &amp;#34;1&amp;#34;, &amp;#34;2&amp;#34; and so on, which never match a header-name filter, so nothing is removed. An application that sends array-form headers and follows an attacker-controlled cross-origin redirect therefore forwards its Authorization, Cookie, and Proxy-Authorization headers verbatim to the attacker-controlled destination, with no error or warning. The sensitiveHeaders option added to fix CVE-2026-40895 / GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the same helper. This is an unauthenticated confidentiality vulnerability: any remote server the victim application contacts can harvest the victim&amp;#39;s credential headers by responding with a cross-origin redirect. This issue has been patched in version…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-111756</guid>
    </item>
    <item>
      <title>GHSA-q3jh-wrc6-jgq8 — follow-redirects array-form headers bypass cross-origin credential stripping</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q3jh-wrc6-jgq8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: follow-redirects&lt;/p&gt;
&lt;p&gt;### Summary
follow-redirects removes sensitive credential headers (Authorization, Proxy-Authorization, Cookie, and any caller-declared `sensitiveHeaders`) before following a redirect that crosses to a different host or downgrades to a less secure protocol. The removal routine iterates the caller&amp;#39;s headers container with `for...in` and matches header names against a filter. This assumes the headers container is a plain object keyed by header names. Node&amp;#39;s underlying `http.request`, which follow-redirects is a drop-in replacement for, also accepts headers as an alternating array of names and values. For an array, `for...in` yields the numeric indices `&amp;#34;0&amp;#34;`, `&amp;#34;1&amp;#34;`, `&amp;#34;2&amp;#34;` and so on, which never match a header-name filter, so nothing is removed. An application that sends array-form headers and follows an attacker-controlled cross-origin redirect therefore forwards its Authorization, Cookie, and Proxy-Authorization headers verbatim to the attacker-controlled destination, with no error or warning. The `sensitiveHeaders` option added to fix CVE-2026-40895 / GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the same helper. This is an unauthenticated confidentiality vulnerability: any remote server the victim application contacts can harvest the victim&amp;#39;s credential headers by responding with a cross-origin redirect.&lt;/p&gt;
&lt;p&gt;### Details
The cross-origin credential-stripping control is implemented by `removeMatchingHeaders(regex, headers)` at `index.js:630-640`:&lt;/p&gt;
&lt;p&gt;```js
function…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: follow-redirects&lt;/p&gt;
&lt;p&gt;### Summary
follow-redirects removes sensitive credential headers (Authorization, Proxy-Authorization, Cookie, and any caller-declared `sensitiveHeaders`) before following a redirect that crosses to a different host or downgrades to a less secure protocol. The removal routine iterates the caller&amp;#39;s headers container with `for...in` and matches header names against a filter. This assumes the headers container is a plain object keyed by header names. Node&amp;#39;s underlying `http.request`, which follow-redirects is a drop-in replacement for, also accepts headers as an alternating array of names and values. For an array, `for...in` yields the numeric indices `&amp;#34;0&amp;#34;`, `&amp;#34;1&amp;#34;`, `&amp;#34;2&amp;#34;` and so on, which never match a header-name filter, so nothing is removed. An application that sends array-form headers and follows an attacker-controlled cross-origin redirect therefore forwards its Authorization, Cookie, and Proxy-Authorization headers verbatim to the attacker-controlled destination, with no error or warning. The `sensitiveHeaders` option added to fix CVE-2026-40895 / GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the same helper. This is an unauthenticated confidentiality vulnerability: any remote server the victim application contacts can harvest the victim&amp;#39;s credential headers by responding with a cross-origin redirect.&lt;/p&gt;
&lt;p&gt;### Details
The cross-origin credential-stripping control is implemented by `removeMatchingHeaders(regex, headers)` at `index.js:630-640`:&lt;/p&gt;
&lt;p&gt;```js
function…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q3jh-wrc6-jgq8</guid>
    </item>
    <item>
      <title>RHSA-2026:88478 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:88478</link>
      <description>&lt;p&gt;follow-redirects: follow-redirects: Information disclosure via improper regular expression escaping in sensitive header filtering follow-redirects: follow-redirects: Information disclosure via array-formatted headers during cross-origin redirects storybook: Storybook: Arbitrary code execution via insufficient message-origin restrictions storybook: storybook: Arbitrary code execution via exposed WebSocket authentication token&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;follow-redirects: follow-redirects: Information disclosure via improper regular expression escaping in sensitive header filtering follow-redirects: follow-redirects: Information disclosure via array-formatted headers during cross-origin redirects storybook: Storybook: Arbitrary code execution via insufficient message-origin restrictions storybook: storybook: Arbitrary code execution via exposed WebSocket authentication token&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:88478</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-111756</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-111756</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: node-follow-redirects, Ubuntu:Pro:20.04:LTS: node-follow-redirects, Ubuntu:Pro:22.04:LTS: node-follow-redirects, Ubuntu:Pro:24.04:LTS: node-follow-redirects, Ubuntu:26.10: node-follow-redirects, Ubuntu:Pro:26.04:LTS: node-follow-redirects&lt;/p&gt;
&lt;p&gt;follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From version 1.16.0 to before version 1.16.1, follow-redirects removes sensitive credential headers (Authorization, Proxy-Authorization, Cookie, and any caller-declared sensitiveHeaders) before following a redirect that crosses to a different host or downgrades to a less secure protocol. The removal routine iterates the caller&amp;#39;s headers container with for...in and matches header names against a filter. This assumes the headers container is a plain object keyed by header names. Node&amp;#39;s underlying http.request, which follow-redirects is a drop-in replacement for, also accepts headers as an alternating array of names and values. For an array, for...in yields the numeric indices &amp;#34;0&amp;#34;, &amp;#34;1&amp;#34;, &amp;#34;2&amp;#34; and so on, which never match a header-name filter, so nothing is removed. An application that sends array-form headers and follows an attacker-controlled cross-origin redirect therefore forwards its Authorization, Cookie, and Proxy-Authorization headers verbatim to the attacker-controlled destination, with no error or warning. The sensitiveHeaders option added to fix CVE-2026-40895 / GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the same helper. This is an unauthenticated confidentiality vulnerability: any remote server the victim application contacts can harvest the victim&amp;#39;s credential headers by responding with a cross-origin redirect. This issue has been patched in version…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: node-follow-redirects, Ubuntu:Pro:20.04:LTS: node-follow-redirects, Ubuntu:Pro:22.04:LTS: node-follow-redirects, Ubuntu:Pro:24.04:LTS: node-follow-redirects, Ubuntu:26.10: node-follow-redirects, Ubuntu:Pro:26.04:LTS: node-follow-redirects&lt;/p&gt;
&lt;p&gt;follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From version 1.16.0 to before version 1.16.1, follow-redirects removes sensitive credential headers (Authorization, Proxy-Authorization, Cookie, and any caller-declared sensitiveHeaders) before following a redirect that crosses to a different host or downgrades to a less secure protocol. The removal routine iterates the caller&amp;#39;s headers container with for...in and matches header names against a filter. This assumes the headers container is a plain object keyed by header names. Node&amp;#39;s underlying http.request, which follow-redirects is a drop-in replacement for, also accepts headers as an alternating array of names and values. For an array, for...in yields the numeric indices &amp;#34;0&amp;#34;, &amp;#34;1&amp;#34;, &amp;#34;2&amp;#34; and so on, which never match a header-name filter, so nothing is removed. An application that sends array-form headers and follows an attacker-controlled cross-origin redirect therefore forwards its Authorization, Cookie, and Proxy-Authorization headers verbatim to the attacker-controlled destination, with no error or warning. The sensitiveHeaders option added to fix CVE-2026-40895 / GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the same helper. This is an unauthenticated confidentiality vulnerability: any remote server the victim application contacts can harvest the victim&amp;#39;s credential headers by responding with a cross-origin redirect. This issue has been patched in version…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-111756</guid>
    </item>
  </channel>
</rss>
