<?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, 09 Oct 2026 00:23:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-265849</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-265849</link>
      <description>EUVD-2026-265849</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-265849</guid>
    </item>
    <item>
      <title>fkie_cve-2025-67647</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-67647</link>
      <description>&lt;p&gt;SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to 2.49.5, SvelteKit is vulnerable to a server side request forgery (SSRF) and denial of service (DoS) under certain conditions. From 2.44.0 through 2.49.4, the vulnerability results in a DoS when your app has at least one prerendered route (export const prerender = true). From 2.19.0 through 2.49.4, the vulnerability results in a DoS when your app has at least one prerendered route and you are using adapter-node without a configured ORIGIN environment variable, and you are not using a reverse proxy that implements Host header validation. This vulnerability is fixed in 2.49.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to 2.49.5, SvelteKit is vulnerable to a server side request forgery (SSRF) and denial of service (DoS) under certain conditions. From 2.44.0 through 2.49.4, the vulnerability results in a DoS when your app has at least one prerendered route (export const prerender = true). From 2.19.0 through 2.49.4, the vulnerability results in a DoS when your app has at least one prerendered route and you are using adapter-node without a configured ORIGIN environment variable, and you are not using a reverse proxy that implements Host header validation. This vulnerability is fixed in 2.49.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-67647</guid>
    </item>
    <item>
      <title>GHSA-j62c-4x62-9r35 — SvelteKit is vulnerable to denial of service and possible SSRF when using prerendering</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j62c-4x62-9r35</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @sveltejs/kit, npm: @sveltejs/adapter-node&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Versions of SvelteKit are vulnerable to a server side request forgery (SSRF) and denial of service (DoS) under certain conditions.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Affected versions from 2.44.0 onwards are vulnerable to DoS if:&lt;/p&gt;
&lt;p&gt;- your app has at least one prerendered route (`export const prerender = true`)&lt;/p&gt;
&lt;p&gt;Affected versions from 2.19.0 onwards are vulnerable to DoS and SSRF if:&lt;/p&gt;
&lt;p&gt;- your app has at least one prerendered route (`export const prerender = true`)
- AND you are using `adapter-node` without a configured `ORIGIN` environment variable, and you are not using a reverse proxy that implements Host header validation&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The DoS causes the running server process to end.&lt;/p&gt;
&lt;p&gt;The SSRF allows access to internal services that can be reached without authentication when fetched from SvelteKit&amp;#39;s server runtime.&lt;/p&gt;
&lt;p&gt;It is also possible to obtain an SXSS via cache poisoning, by forcing a potential CDN to cache an XSS returned by the attacker&amp;#39;s server (the latter being able to specify the cache-control of their choice).&lt;/p&gt;
&lt;p&gt;### Credits
- Allam Rachid ([zhero;](https://zhero-web-sec.github.io/research-and-things/))
- Allam Yasser (inzo)
- d-xuan ([wednesday](https://d-xuan.github.io/wednesday/))&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @sveltejs/kit, npm: @sveltejs/adapter-node&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Versions of SvelteKit are vulnerable to a server side request forgery (SSRF) and denial of service (DoS) under certain conditions.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Affected versions from 2.44.0 onwards are vulnerable to DoS if:&lt;/p&gt;
&lt;p&gt;- your app has at least one prerendered route (`export const prerender = true`)&lt;/p&gt;
&lt;p&gt;Affected versions from 2.19.0 onwards are vulnerable to DoS and SSRF if:&lt;/p&gt;
&lt;p&gt;- your app has at least one prerendered route (`export const prerender = true`)
- AND you are using `adapter-node` without a configured `ORIGIN` environment variable, and you are not using a reverse proxy that implements Host header validation&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The DoS causes the running server process to end.&lt;/p&gt;
&lt;p&gt;The SSRF allows access to internal services that can be reached without authentication when fetched from SvelteKit&amp;#39;s server runtime.&lt;/p&gt;
&lt;p&gt;It is also possible to obtain an SXSS via cache poisoning, by forcing a potential CDN to cache an XSS returned by the attacker&amp;#39;s server (the latter being able to specify the cache-control of their choice).&lt;/p&gt;
&lt;p&gt;### Credits
- Allam Rachid ([zhero;](https://zhero-web-sec.github.io/research-and-things/))
- Allam Yasser (inzo)
- d-xuan ([wednesday](https://d-xuan.github.io/wednesday/))&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j62c-4x62-9r35</guid>
    </item>
  </channel>
</rss>
