NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-128120: SvelteKit: DoS while parsing form data from a remote functions `form`

highCVSS 3.1 7.5GHSA-3r8g-jcqq-3p5j

SvelteKit apps that use the experimental remote functions feature can be frozen by one crafted request. Parsing form data for a remote form, query or command blocks the event loop for a long time. It affects @sveltejs/kit 2.42.0 through 3.1.0 and is fixed in 3.1.1.

Published Nov 16, 2026 · Analysis Nov 16, 2026

What an attacker can do

Remote functions are an experimental SvelteKit feature enabled by a flag. When an app uses the form, query or command functions, the server parses the incoming request data. A specially crafted request makes that parsing take a very long time, which is an algorithmic-complexity flaw (CWE-407).

Node.js runs JavaScript on one event loop. While the parser works, the server cannot answer other requests. An attacker needs only network access to the endpoint, with no login. Repeating the request keeps the app unavailable.

The flaw gives no data access or code execution. It affects availability only. The 3.1.1 release notes say remote form submissions are now parsed in linear time.

Who is affected

@sveltejs/kit >= 2.42.0 and <= 3.1.0, and only apps that turn on the experimental remote functions flag and use form, query or command remote functions. Apps without the flag are not exposed through this path.

Check the installed version:

npm ls @sveltejs/kit

Then look in svelte.config.js for the experimental remote functions option and for .remote.js or .remote.ts files.

@sveltejs/kit

Ecosystem
npm
Affected
>= 2.42.0, <= 3.1.0
Fixed in
3.1.1
Check
npm ls @sveltejs/kit

How to fix it

Upgrade to @sveltejs/kit 3.1.1:

npm install @sveltejs/[email protected]

The advisory lists no workaround. If you cannot upgrade at once, switching off the experimental remote functions flag removes the exposed parsing, though it may break features that depend on it. Request-size limits at a reverse proxy may reduce the impact, but the sources do not say they stop the attack.

How to tell if you were hit

Look for sudden event loop stalls: requests that hang while CPU stays pinned on one Node process, health checks that time out, and a process restarting under a supervisor. Compare with access logs for unusually large or oddly shaped POST bodies to remote function endpoints just before the stall. The advisory describes no specific log line.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

This only affects applications using the experimental remote functions flag and utilizing the form, query, or command remote functions. A specially-crafted request could block the event loop for extended periods of time during parsing.

Credited to elliott-with-the-longest-name-on-github, Rich-Harris.

Questions

Am I affected if I do not use remote functions?

No, per the advisory. It applies only to apps that use the experimental remote functions flag together with form, query or command functions.

Which version fixes CVE-2026-128120?

@sveltejs/kit 3.1.1. Affected versions run from 2.42.0 through 3.1.0.

Can it lead to data theft?

No. The CVSS vector shows only an availability impact. The result is a blocked event loop and denial of service.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More npm vulnerabilities

All npm entries