GHSA-VRHM-GVG7-FPCF

GHSA-VRHM-GVG7-FPCF is a medium-severity allocation of resources without limits or throttling vulnerability in @sveltejs/kit (npm), affecting versions >= 2.49.0, <= 2.52.1. It is fixed in 2.52.2.

Summary

Versions of @sveltejs/kit prior to 2.52.2 with remote functions enabled can be vulnerable to memory exhaustion. Malformed form data can cause the server process to crash due to excessive memory allocation, resulting in denial of service.

Only applications using both experimental.remoteFunctions and form are vulnerable.

Impact

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

Affected versions

@sveltejs/kit (>= 2.49.0, <= 2.52.1)

Security releases

@sveltejs/kit → 2.52.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade @sveltejs/kit to 2.52.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-VRHM-GVG7-FPCF? GHSA-VRHM-GVG7-FPCF is a medium-severity allocation of resources without limits or throttling vulnerability in @sveltejs/kit (npm), affecting versions >= 2.49.0, <= 2.52.1. It is fixed in 2.52.2. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
  2. Which versions of @sveltejs/kit are affected by GHSA-VRHM-GVG7-FPCF? @sveltejs/kit (npm) versions >= 2.49.0, <= 2.52.1 is affected.
  3. Is there a fix for GHSA-VRHM-GVG7-FPCF? Yes. GHSA-VRHM-GVG7-FPCF is fixed in 2.52.2. Upgrade to this version or later.
  4. Is GHSA-VRHM-GVG7-FPCF exploitable, and should I be worried? Whether GHSA-VRHM-GVG7-FPCF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether GHSA-VRHM-GVG7-FPCF is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix GHSA-VRHM-GVG7-FPCF? Upgrade @sveltejs/kit to 2.52.2 or later.

Other vulnerabilities in @sveltejs/kit

Stop the waste.
Protect your environment with Kodem.