<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Sveltekit — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/sveltekit/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sat, 11 Apr 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/sveltekit/feed.xml" rel="self" type="application/rss+xml"/><item><title>@sveltejs/adapter-node BODY_SIZE_LIMIT Bypass Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-04-sveltekit-body-bypass/</link><pubDate>Sat, 11 Apr 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-sveltekit-body-bypass/</guid><description>A vulnerability exists in @sveltejs/adapter-node where requests could bypass the `BODY_SIZE_LIMIT` on SvelteKit applications, potentially leading to denial of service.</description><content:encoded><![CDATA[<p>A high-severity vulnerability, CVE-2026-40073, affects SvelteKit applications using <code>@sveltejs/adapter-node</code> versions 2.57.0 and earlier. This vulnerability allows requests to bypass the intended <code>BODY_SIZE_LIMIT</code>, potentially leading to resource exhaustion and denial-of-service conditions. The bypass occurs specifically within the adapter itself and does not impact body size limits enforced by other layers such as Web Application Firewalls (WAFs), gateways, or platform-level configurations. Successful exploitation could allow an attacker to send arbitrarily large requests, overwhelming the server and causing it to become unresponsive. The vulnerability was patched in version 2.57.1.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker identifies a SvelteKit application using a vulnerable version of <code>@sveltejs/adapter-node</code> (&lt;= 2.57.0).</li>
<li>The attacker crafts an HTTP request with a body exceeding the configured <code>BODY_SIZE_LIMIT</code>.</li>
<li>Due to the vulnerability, the adapter fails to enforce the size limit on the request body.</li>
<li>The oversized request is processed by the SvelteKit application.</li>
<li>The application consumes excessive server resources (CPU, memory) while handling the oversized request.</li>
<li>The server becomes overloaded and unresponsive due to resource exhaustion.</li>
<li>Legitimate users are unable to access the application, resulting in a denial-of-service condition.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability can lead to a denial-of-service condition, rendering the SvelteKit application unavailable to legitimate users. The number of affected applications is potentially large, given the popularity of SvelteKit for web development. Sectors utilizing SvelteKit for their web applications are all potentially at risk. If exploited, the application’s server can become overloaded causing a significant impact to availability.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade <code>@sveltejs/kit</code> to version 2.57.1 or later to remediate CVE-2026-40073.</li>
<li>Monitor web server logs for unusually large HTTP request sizes, using a rule such as the example Sigma rule below.</li>
<li>Implement or reinforce body size limits at other layers of the application stack (e.g., WAF, gateway) to provide defense-in-depth.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>sveltekit</category><category>denial-of-service</category><category>vulnerability</category></item></channel></rss>