<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T09:26:20.825267+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-406477</id>
    <title>EUVD-2026-406477</title>
    <updated>2026-11-17T09:26:20.826965+00:00</updated>
    <content>EUVD-2026-406477</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-406477"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hf59-9xwc-2g4p</id>
    <title>GHSA-hf59-9xwc-2g4p — Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)</title>
    <updated>2026-11-17T09:26:20.826998+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: nuxt, npm: @nuxt/nitro-server</p>
<p>### Summary</p>
<p>The fix for CVE-2026-46342 (GHSA-g8wj-3cr3-6w7v) binds each `/__nuxt_island/&lt;Name&gt;_&lt;hash&gt;.json` path to its props by hashing the `(name, props, context, source)` tuple. That hash was computed over `ohash`'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's path and render different content at that path.</p>
<p>### Impact</p>
<p>For example, these two prop objects serialize identically and share one island path:</p>
<p>```js
{ html: '', note: '&lt;img src=x onerror="alert(1)"&gt;' }
{ html: '\',note:\'&lt;img src=x onerror="alert(1)"&gt;' }
```</p>
<p>This reopens the scenarios described in GHSA-g8wj-3cr3-6w7v:</p>
<p>- **`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.</p>
<p>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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hf59-9xwc-2g4p"/>
  </entry>
</feed>
