SvelteKit versions from 2.49.0 through 2.53.2 (fixed in 2.53.3) contain a deserialization expansion issue in the experimental form remote function. When an application enables experimental.remoteFunctions and uses the form function to process the files array without validating files.length or individual file sizes, an attacker can submit relatively small inputs that expand into very large file arrays, leading to expensive processing and denial of service.
CVE-2026-82259
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 28, 2026SvelteKit 2.49.0 before 2.53.3 Denial of Service via form | Advisories | VulnCheck
https://www.vulncheck.com/advisories/sveltekit-2.49.0-before-2.53.3-denial-of-service-via-formDeserialization expansion in unvalidated SvelteKit `form` remote function leads to denial of service (experimental only) · Advisory · sveltejs/kit · GitHub
https://github.com/sveltejs/kit/security/advisories/GHSA-fpg4-jhqr-589cVendor Advisories for CVE-2026-82259(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-29 06:25 UTCGHSA enrichment
- 2026-08-28 19:03 UTCGHSA enrichment
- 2026-08-28 16:36 UTCEG score recompute
- 2026-08-28 16:35 UTCGHSA enrichment
- 2026-08-28 15:37 UTCEG score recompute
- 2026-08-28 15:37 UTCGHSA enrichment
- 2026-08-28 12:22 UTCEG score recompute
- 2026-08-28 11:22 UTCEG score recompute
- 2026-08-28 11:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-10992EG 9.8EPSS p95CRITICAL
- CVE-2013-4521EG 9.8EPSS p90CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS p98CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-10934EG 9.8CRITICAL
- CVE-2016-9498EG 9.8EPSS p97CRITICAL
- CVE-2016-9483EG 9.8CRITICAL
- CVE-2015-2020EG 9.8CRITICAL
- CVE-2017-15692EG 9.8EPSS p91CRITICAL
Frequently asked(4)
What is CVE-2026-82259?
When was CVE-2026-82259 disclosed?
What is the CVSS score of CVE-2026-82259?
How do I remediate CVE-2026-82259?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82259
Is Your Infrastructure Affected by CVE-2026-82259?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.