<?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 03:24:24 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-406476</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-406476</link>
      <description>EUVD-2026-406476</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-406476</guid>
    </item>
    <item>
      <title>GHSA-96x6-fvhx-49hg — Nuxt exposes the message and data of unhandled errors thrown during server rendering</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-96x6-fvhx-49hg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An application is affected if server-rendered code lets an error with sensitive details reach the error page, for example:&lt;/p&gt;
&lt;p&gt;```vue
&amp;lt;script setup lang=&amp;#34;ts&amp;#34;&amp;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}`)
&amp;lt;/script&amp;gt;
```&lt;/p&gt;
&lt;p&gt;Anyone who can make the request fail (for example by requesting an id the upstream service rejects) receives `[GET] &amp;#34;http://users.internal/users/1?token=...&amp;#34;: 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.&lt;/p&gt;
&lt;p&gt;The same applies to any other error thrown during server rendering, such as a database driver error whose message names an internal host.&lt;/p&gt;
&lt;p&gt;Errors created deliberately with `createError` (or `showError`) are not affected: t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An application is affected if server-rendered code lets an error with sensitive details reach the error page, for example:&lt;/p&gt;
&lt;p&gt;```vue
&amp;lt;script setup lang=&amp;#34;ts&amp;#34;&amp;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}`)
&amp;lt;/script&amp;gt;
```&lt;/p&gt;
&lt;p&gt;Anyone who can make the request fail (for example by requesting an id the upstream service rejects) receives `[GET] &amp;#34;http://users.internal/users/1?token=...&amp;#34;: 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.&lt;/p&gt;
&lt;p&gt;The same applies to any other error thrown during server rendering, such as a database driver error whose message names an internal host.&lt;/p&gt;
&lt;p&gt;Errors created deliberately with `createError` (or `showError`) are not affected: t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-96x6-fvhx-49hg</guid>
    </item>
  </channel>
</rss>
