We’ve released patches for 5 vulnerabilities across devalue, svelte, @sveltejs/kit, and @sveltejs/adapter-node. Here’s what you need to know:
Upgrade now
If you’re using any of these packages, upgrade them to their corresponding non-vulnerable versions:
devalue:5.6.2svelte:5.46.4@sveltejs/kit:2.49.5@sveltejs/adapter-node:5.5.1
For cross-dependent packages — svelte and @sveltejs/kit depend on devalue — patched versions already include upgraded dependencies.
We’re extremely thankful to all of the security researchers who responsibly disclosed these vulnerabilities and worked with us to get them fixed, to the security team at Vercel who helped us navigate the disclosure process, and to the maintainers who worked to publish the fixes.
Over the last few weeks, we’ve seen a spate of high profile vulnerabilities affecting popular tools across the web development ecosystem. While they are unfortunate, it has been encouraging to see the community pulling together to keep end users safe. Using the lessons learned from these vulnerabilities, we will invest in processes that will help catch future bugs during the writing and review phases, before they go live.
If you think you have discovered a vulnerability in a package maintained by the Svelte team, we urge you to privately report it via the Security tab on the repo in question (or the Svelte repo, if unsure).
Details
Full reports are available in the published security advisories, but we’ve included a brief summary of each below.
CVE-2026-22775: DoS in devalue.parse due to memory/CPU exhaustion
- Packages affected:
- You’re affected if:
- You’re using
devalueversions5.1.0through5.6.1, and - You’re parsing user-controlled input
- You’re using
- Effects:
- A malicious payload can cause arbitrarily large memory allocation, potentially crashing the process
- SvelteKit applications using remote functions are vulnerable, as the parameters are run through
devalue.parse - If you don’t have remote functions enabled, SvelteKit is not vulnerable
CVE-2026-22774: DoS in devalue.parse due to memory exhaustion
(Yes, this is very similar to the previous CVE. No, it is not the same!)
- Packages affected:
- You’re affected if:
- You’re using
devalueversions5.3.0through5.6.1, and - You’re parsing user-controlled input
- You’re using
- Effects:
- A malicious payload can cause arbitrarily large memory allocation, potentially crashing the process
- SvelteKit applications using remote functions are vulnerable, as the parameters are run through
devalue.parse - If you don’t have remote functions enabled, SvelteKit is not vulnerable
CVE-2026-22803: Memory amplification DoS in Remote Functions binary form deserializer
- Packages affected:
- You’re affected if:
- You’re using SvelteKit versions
2.49.0through2.49.4, and - You’ve enabled the
experimental.remoteFunctionsflag, and - You’re using
form
- You’re using SvelteKit versions
- Effects:
- Users can submit a malicious request that causes your application to hang and allocate arbitrarily-large amounts of memory
CVE-2025-67647: Denial of service and possible SSRF when using prerendering
- Packages affected:
@sveltejs/kit@sveltejs/adapter-node
- You’re vulnerable to DoS if:
- You’re using
@sveltejs/kitversions2.44.0through2.49.4, and - Your app has at least one prerendered route
- You’re using
- You’re vulnerable to DoS and SSRF if:
- You’ve using
@sveltejs/kitversions2.19.0through2.49.4, and - Your app has at least one prerendered route, and
- You’re using
@sveltejs/adapter-nodewithout a configuredORIGINenvironment variable, and you are not using a reverse proxy that implements Host header validation
- You’ve using
- Effects:
- DoS causes the server process to die
- SSRF allows access to internal resources that can be reached without authentication from SvelteKit’s server runtime
- If the stars align, it’s possible to obtain SXSS via cache poisoning by forcing a potential CDN to cache an XSS returned by the attacker’s server (the latter being able to specify the cache-control of their choice)
CVE-2025-15265: XSS via hydratable
- Packages affected:
- You’re vulnerable if:
- You’re using
svelteversions2.46.0through2.46.3, and - You’re using
hydratable, and you’re passing unsanitized, user-controlled strings in as keys
- You’re using
- Effects:
- Your users are vulnerable to XSS if an attacker can manage to get a controlled key into
hydratablethat is then returned to another user
- Your users are vulnerable to XSS if an attacker can manage to get a controlled key into