<?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-17T03:46:11.107150+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-406476</id>
    <title>EUVD-2026-406476</title>
    <updated>2026-11-17T03:46:11.108988+00:00</updated>
    <content>EUVD-2026-406476</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-406476"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-96x6-fvhx-49hg</id>
    <title>GHSA-96x6-fvhx-49hg — Nuxt exposes the message and data of unhandled errors thrown during server rendering</title>
    <updated>2026-11-17T03:46:11.109025+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: nuxt</p>
<p>### Summary</p>
<p>When a page, plugin or route middleware throws an error that is not an HTTP error, Nuxt wraps it with `createError` before rendering the error page. The wrapped error was treated as one the app raised deliberately, so in production its `message` and `data` were sent to the client in the error page payload (`__NUXT_DATA__`) and in JSON error responses. For a failed `$fetch`, that is the URL that was requested (including its query string) and the body of the upstream error response.</p>
<p>### Impact</p>
<p>An application is affected if server-rendered code lets an error with sensitive details reach the error page, for example:</p>
<p>```vue
&lt;script setup lang="ts"&gt;
const route = useRoute()
// the upstream error body, and the token in the URL, reach the client if this request fails
await $fetch(`http://users.internal/users/${route.params.id}?token=${useRuntimeConfig().usersToken}`)
&lt;/script&gt;
```</p>
<p>Anyone who can make the request fail (for example by requesting an id the upstream service rejects) receives `[GET] "http://users.internal/users/1?token=...": 502` and the upstream response body. This happens regardless of what a custom `error.vue` renders, because the details are part of the payload. With the default configuration, the HTTP status line is not affected.</p>
<p>The same applies to any other error thrown during server rendering, such as a database driver error whose message names an internal host.</p>
<p>Errors created deliberately with `createError` (or `showError`) are not affected: t…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-96x6-fvhx-49hg"/>
  </entry>
</feed>
