How severe is GHSA-vrhm-gvg7-fpcf?

No CVSS score has been assigned to GHSA-vrhm-gvg7-fpcf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vrhm-gvg7-fpcf?

GHSA-vrhm-gvg7-fpcf affects the following packages: @sveltejs/kit (npm). Ecosystems affected: npm.

How do I fix GHSA-vrhm-gvg7-fpcf?

Update @sveltejs/kit to 2.52.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vrhm-gvg7-fpcf is resolved across your whole dependency graph.

How do I detect GHSA-vrhm-gvg7-fpcf in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sveltejs/kit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vrhm-gvg7-fpcf if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-vrhm-gvg7-fpcf actively exploited in the wild?

No public exploit code has been indexed for GHSA-vrhm-gvg7-fpcf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-vrhm-gvg7-fpcf?

GHSA-vrhm-gvg7-fpcf has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vrhm-gvg7-fpcf?

GHSA-vrhm-gvg7-fpcf is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vrhm-gvg7-fpcf published, and has it been updated?

GHSA-vrhm-gvg7-fpcf was published on February 19, 2026 and was last updated on September 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Memory exhaustion in SvelteKit remote form deserialization (experimental only)GHSA-vrhm-gvg7-fpcf

Fix: sveltejs/kit@f47c01b

GHSA-vrhm-gvg7-fpcf is a Uncontrolled Resource Consumption vulnerability in @sveltejs/kit. A fix is available for @sveltejs/kit — see the affected versions and patch details below.

Also known asCVE-2026-82260

Published

Feb 19, 2026

Updated

Sep 2, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vrhm-gvg7-fpcf.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

216other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@sveltejs/kitnpm

4.7Mdownloads / week

Description

SvelteKit (@sveltejs/kit) versions >=2.49.0 and <=2.52.1 with experimental remote functions (experimental.remoteFunctions) and form enabled contain a memory exhaustion vulnerability in remote form deserialization. Malformed form data can cause excessive memory allocation, crashing the server process and resulting in denial of service. Fixed in 2.52.2.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@sveltejs/kit`	≥ 2.49.0&&< 2.52.2	2.52.2`npm install @sveltejs/kit@2.52.2`

Affected Products

1 product · 1 configurations

Application

sveltekitsvelte

≥ 2.49.0 && < 2.52.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sveltejs/kit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @sveltejs/kit to 2.52.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vrhm-gvg7-fpcf is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-vrhm-gvg7-fpcf in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works