Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-82260 – Denial of Service (Memory Exhaustion) – SvelteKit (@sveltejs/kit) 2.49.0–2.52.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82260 is an uncontrolled resource consumption (CWE-400) vulnerability in SvelteKit’s (@sveltejs/kit) experimental remote functions feature. When an application enables both experimental.remoteFunctions and remote form handling, an attacker can send malformed form data over the network that triggers excessive memory allocation during deserialization, crashing the server process. The issue carries a CVSS score of 8.7 and results in denial of service with no authentication or user interaction required.

Technical details

  • Root cause: the remote form deserialization logic in SvelteKit’s remote functions implementation does not bound memory allocation when parsing submitted form data.
  • Trigger condition: the target application must have both experimental.remoteFunctions and remote form handling enabled; a crafted/malformed form submission is then required.
  • Attack vector: network-based, unauthenticated, no user interaction, low attack complexity.
  • Impact: high availability impact (server crash / denial of service); no confidentiality or integrity impact.

Affected software

  • @sveltejs/kit (npm) versions >= 2.49.0 and <= 2.52.1, when experimental.remoteFunctions and remote form are both enabled.
  • Fixed in @sveltejs/kit version 2.52.2.

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
  • An associated CVSS v4.0 score of 8.7 has also been recorded for this vulnerability, reflecting the same network-exploitable, high-availability-impact characteristics.

Mitigation and recommended actions

  • Immediate: Upgrade @sveltejs/kit to version 2.52.2 or later.
  • If patching is not immediately possible: disable experimental.remoteFunctions and/or remote form handling until the upgrade can be applied; verify the deployed version with npm list @sveltejs/kit and restart the application server after upgrading.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /_app/immutable/entry/start.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge