<?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>Tue, 06 Oct 2026 09:58:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-9678 — undici vulnerable to cross-user information disclosure via shared cache whitespace bypass</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-9678</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; undici&lt;/p&gt;
&lt;p&gt;Impact:
Undici&amp;#39;s cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=&amp;#34; authorization&amp;#34; or no-cache=&amp;#34;\tauthorization&amp;#34;. The parser preserves the surrounding whitespace, so later comparisons against the literal authorization field name fail and the response is stored.&lt;/p&gt;
&lt;p&gt;In shared-cache mode, this allows a response containing one user&amp;#39;s authenticated data to be served from cache to a subsequent caller, including an unauthenticated caller, when both requests resolve to the same cache key.&lt;/p&gt;
&lt;p&gt;Affected applications are those that explicitly enable the cache interceptor (interceptors.cache()) in shared mode, forward Authorization headers upstream, and receive cacheable responses with non-canonical qualified private or no-cache directives.&lt;/p&gt;
&lt;p&gt;Patches:
Upgrade to undici v7.28.0 or v8.5.0.&lt;/p&gt;
&lt;p&gt;Workarounds:
If upgrade is not immediately possible, disable shared-cache mode for traffic that includes Authorization headers, avoid caching responses to authenticated requests, or add Vary: Authorization upstream.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; undici&lt;/p&gt;
&lt;p&gt;Impact:
Undici&amp;#39;s cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=&amp;#34; authorization&amp;#34; or no-cache=&amp;#34;\tauthorization&amp;#34;. The parser preserves the surrounding whitespace, so later comparisons against the literal authorization field name fail and the response is stored.&lt;/p&gt;
&lt;p&gt;In shared-cache mode, this allows a response containing one user&amp;#39;s authenticated data to be served from cache to a subsequent caller, including an unauthenticated caller, when both requests resolve to the same cache key.&lt;/p&gt;
&lt;p&gt;Affected applications are those that explicitly enable the cache interceptor (interceptors.cache()) in shared mode, forward Authorization headers upstream, and receive cacheable responses with non-canonical qualified private or no-cache directives.&lt;/p&gt;
&lt;p&gt;Patches:
Upgrade to undici v7.28.0 or v8.5.0.&lt;/p&gt;
&lt;p&gt;Workarounds:
If upgrade is not immediately possible, disable shared-cache mode for traffic that includes Authorization headers, avoid caching responses to authenticated requests, or add Vary: Authorization upstream.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-9678</guid>
    </item>
  </channel>
</rss>
