<?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, 17 Nov 2026 02:33:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-406477</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-406477</link>
      <description>EUVD-2026-406477</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-406477</guid>
    </item>
    <item>
      <title>GHSA-hf59-9xwc-2g4p — Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hf59-9xwc-2g4p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt, npm: @nuxt/nitro-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The fix for CVE-2026-46342 (GHSA-g8wj-3cr3-6w7v) binds each `/__nuxt_island/&amp;lt;Name&amp;gt;_&amp;lt;hash&amp;gt;.json` path to its props by hashing the `(name, props, context, source)` tuple. That hash was computed over `ohash`&amp;#39;s serialization, which does not escape quotes inside strings or delimiters inside keys, so two different prop objects can produce the same hash. A request with crafted props can therefore pass validation for another island&amp;#39;s path and render different content at that path.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;For example, these two prop objects serialize identically and share one island path:&lt;/p&gt;
&lt;p&gt;```js
{ html: &amp;#39;&amp;#39;, note: &amp;#39;&amp;lt;img src=x onerror=&amp;#34;alert(1)&amp;#34;&amp;gt;&amp;#39; }
{ html: &amp;#39;\&amp;#39;,note:\&amp;#39;&amp;lt;img src=x onerror=&amp;#34;alert(1)&amp;#34;&amp;gt;&amp;#39; }
```&lt;/p&gt;
&lt;p&gt;This reopens the scenarios described in GHSA-g8wj-3cr3-6w7v:&lt;/p&gt;
&lt;p&gt;- **`nuxt generate` / prerendering.** Nuxt caches prerendered island responses by path. If the crawler reaches a link to the colliding URL (for example in user-submitted content included in the build) before it renders the page that uses the legitimate props, the colliding response is written into the generated page.
- **Path-keyed shared caches.** A CDN or reverse proxy that caches `/__nuxt_island/*` by path only, ignoring the query, can be primed with the colliding response.&lt;/p&gt;
&lt;p&gt;An attacker has to construct props that collide with a specific legitimate tuple, which in practice means at least part of that tuple is a string they control (for example a stored comment or profile field passed as a prop). Where a prop reaches a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt, npm: @nuxt/nitro-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The fix for CVE-2026-46342 (GHSA-g8wj-3cr3-6w7v) binds each `/__nuxt_island/&amp;lt;Name&amp;gt;_&amp;lt;hash&amp;gt;.json` path to its props by hashing the `(name, props, context, source)` tuple. That hash was computed over `ohash`&amp;#39;s serialization, which does not escape quotes inside strings or delimiters inside keys, so two different prop objects can produce the same hash. A request with crafted props can therefore pass validation for another island&amp;#39;s path and render different content at that path.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;For example, these two prop objects serialize identically and share one island path:&lt;/p&gt;
&lt;p&gt;```js
{ html: &amp;#39;&amp;#39;, note: &amp;#39;&amp;lt;img src=x onerror=&amp;#34;alert(1)&amp;#34;&amp;gt;&amp;#39; }
{ html: &amp;#39;\&amp;#39;,note:\&amp;#39;&amp;lt;img src=x onerror=&amp;#34;alert(1)&amp;#34;&amp;gt;&amp;#39; }
```&lt;/p&gt;
&lt;p&gt;This reopens the scenarios described in GHSA-g8wj-3cr3-6w7v:&lt;/p&gt;
&lt;p&gt;- **`nuxt generate` / prerendering.** Nuxt caches prerendered island responses by path. If the crawler reaches a link to the colliding URL (for example in user-submitted content included in the build) before it renders the page that uses the legitimate props, the colliding response is written into the generated page.
- **Path-keyed shared caches.** A CDN or reverse proxy that caches `/__nuxt_island/*` by path only, ignoring the query, can be primed with the colliding response.&lt;/p&gt;
&lt;p&gt;An attacker has to construct props that collide with a specific legitimate tuple, which in practice means at least part of that tuple is a string they control (for example a stored comment or profile field passed as a prop). Where a prop reaches a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hf59-9xwc-2g4p</guid>
    </item>
  </channel>
</rss>
