<?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:10:29 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-380617</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-380617</link>
      <description>EUVD-2026-380617</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-380617</guid>
    </item>
    <item>
      <title>fkie_cve-2026-103004</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-103004</link>
      <description>&lt;p&gt;Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a &amp;#39;use cache&amp;#39; function that calls another &amp;#39;use cache&amp;#39; function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function&amp;#39;s cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further.&lt;/p&gt;
&lt;p&gt;What values are leaked cannot be attacker controlled. Which value&amp;#39;s content is served depends only on which invocation wrote the entry first.&lt;/p&gt;
&lt;p&gt;This has been patched in 16.3.8.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a &amp;#39;use cache&amp;#39; function that calls another &amp;#39;use cache&amp;#39; function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function&amp;#39;s cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further.&lt;/p&gt;
&lt;p&gt;What values are leaked cannot be attacker controlled. Which value&amp;#39;s content is served depends only on which invocation wrote the entry first.&lt;/p&gt;
&lt;p&gt;This has been patched in 16.3.8.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-103004</guid>
    </item>
  </channel>
</rss>
