<?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 13:24:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-13697 — undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-13697</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; undici&lt;/p&gt;
&lt;p&gt;undici&amp;#39;s cache interceptor mishandles malformed Cache-Control private directives. In undici 7.0.0 up to before 7.29.0 and 8.0.0 up to before 8.9.0, a response carrying a degenerate qualified private directive, such as private set to an empty value, can be stored in the default shared cache and later served to a different caller with the same cache key, disclosing private response bodies and headers including Set-Cookie. Separately, a Cache-Control header that combines an unqualified private directive with a qualified one triggers an uncaught TypeError in the cache-control parser, which rejects the request and, depending on the consumer&amp;#39;s error handling, can terminate the process. Both issues affect applications using the cache interceptor in shared mode, including the default configuration. The issues are fixed in undici 7.29.0 and 8.9.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; undici&lt;/p&gt;
&lt;p&gt;undici&amp;#39;s cache interceptor mishandles malformed Cache-Control private directives. In undici 7.0.0 up to before 7.29.0 and 8.0.0 up to before 8.9.0, a response carrying a degenerate qualified private directive, such as private set to an empty value, can be stored in the default shared cache and later served to a different caller with the same cache key, disclosing private response bodies and headers including Set-Cookie. Separately, a Cache-Control header that combines an unqualified private directive with a qualified one triggers an uncaught TypeError in the cache-control parser, which rejects the request and, depending on the consumer&amp;#39;s error handling, can terminate the process. Both issues affect applications using the cache interceptor in shared mode, including the default configuration. The issues are fixed in undici 7.29.0 and 8.9.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-13697</guid>
    </item>
    <item>
      <title>GHSA-f88m-g3jw-g9cj — sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f88m-g3jw-g9cj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: sharp&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A number of vulnerabilities, two rated as &amp;#34;High&amp;#34; severity using CVSSv4, have been discovered and fixed in the upstream libvips dependency.&lt;/p&gt;
&lt;p&gt;Those processing untrusted input with versions of sharp prior to 0.35.0 are affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;#### Using prebuilt binaries provided by sharp?&lt;/p&gt;
&lt;p&gt;Most people rely on the prebuilt binaries provided by sharp.&lt;/p&gt;
&lt;p&gt;Please upgrade sharp to the latest version, currently 0.35.3, which provides libvips 8.18.3.&lt;/p&gt;
&lt;p&gt;#### Using a globally-installed libvips?&lt;/p&gt;
&lt;p&gt;Please ensure you are using the latest libvips 8.18.3.&lt;/p&gt;
&lt;p&gt;### Workarounds
Add the following to your code to prevent sharp from decoding GIF, TIFF and VIPS images.
```js
sharp.block({ operation: [&amp;#34;VipsForeignLoadNsgif&amp;#34;, &amp;#34;VipsForeignLoadTiff&amp;#34;, &amp;#34;VipsForeignLoadVips&amp;#34;] });
```&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: sharp&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A number of vulnerabilities, two rated as &amp;#34;High&amp;#34; severity using CVSSv4, have been discovered and fixed in the upstream libvips dependency.&lt;/p&gt;
&lt;p&gt;Those processing untrusted input with versions of sharp prior to 0.35.0 are affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;#### Using prebuilt binaries provided by sharp?&lt;/p&gt;
&lt;p&gt;Most people rely on the prebuilt binaries provided by sharp.&lt;/p&gt;
&lt;p&gt;Please upgrade sharp to the latest version, currently 0.35.3, which provides libvips 8.18.3.&lt;/p&gt;
&lt;p&gt;#### Using a globally-installed libvips?&lt;/p&gt;
&lt;p&gt;Please ensure you are using the latest libvips 8.18.3.&lt;/p&gt;
&lt;p&gt;### Workarounds
Add the following to your code to prevent sharp from decoding GIF, TIFF and VIPS images.
```js
sharp.block({ operation: [&amp;#34;VipsForeignLoadNsgif&amp;#34;, &amp;#34;VipsForeignLoadTiff&amp;#34;, &amp;#34;VipsForeignLoadVips&amp;#34;] });
```&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f88m-g3jw-g9cj</guid>
    </item>
  </channel>
</rss>
