Quick answers
- Is CVE-2026-82260 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82260 being exploited in the wild.
- How severe is CVE-2026-82260?
- High severity, with a CVSS score of 7.5, published 28 August 2026.
- Which products and versions are affected?
- @sveltejs/kit (npm) SEMVER:introduced=2.49.0,fixed=2.52.2.
- Is there a fix for CVE-2026-82260?
- Yes. @sveltejs/kit (npm): upgrade to 2.52.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82260 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82260?
- Check whether you run @sveltejs/kit (npm) or SvelteKit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @sveltejs/kit (npm): upgrade to 2.52.2 or later
npm install @sveltejs/kit@2.52.2
Technical details
This vulnerability is a memory exhaustion / denial-of-service issue (CWE-770) in SvelteKit's binary form deserialization logic. The vulnerability affects versions 2.49.0 through 2.52.1 when both experimental.remoteFunctions and form handling are enabled. An unauthenticated attacker on the network can send crafted form data that triggers excessive memory allocation during deserialization, crashing the server process without requiring authentication or user interaction. The fix, released in version 2.52.2, implements stricter parsing of the file offset table during binary form deserialization.
Affected products
- Svelte @sveltejs/kit 2.49.0 through 2.52.1
Identifiers
- CVE-2026-82260
- GHSA-vrhm-gvg7-fpcf
Timeline
- 2026-02-19: disclosed: GHSA-vrhm-gvg7-fpcf and CVE-2026-82260 published
- 2026-02-18: patched: Fix merged (commit f47c01bd) targeting version 2.52.2