{"answers":{"affected":"2 open source packages ship an affected version, including @sveltejs/kit. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-82260 in the wild and no public exploit code.","fix":"Upgrade @sveltejs/kit to 2.52.2 or later.","what":"CVE-2026-82260 is a high-severity denial of service vulnerability in sveltejs kit, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-82260 and fix it if it is affected.\n\nWhat it is: CVE-2026-82260 is a high-severity denial of service vulnerability in sveltejs kit, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-82260 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @sveltejs/kit (npm): affected from 2.49.0; fixed in 2.52.2\n- @sveltejs/kit (npm): affected from 2.49.0; fixed in 2.52.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-82260/ (Markdown: https://insights.sbomify.com/CVE-2026-82260/index.md)","id":"CVE-2026-82260","markdown":"https://insights.sbomify.com/CVE-2026-82260/index.md","name":"CVE-2026-82260","record":{"aliases":["GHSA-33c7-c62f-7cc2","GHSA-vrhm-gvg7-fpcf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"SvelteKit web framework","requires_auth":"none","summary":"Attackers can crash SvelteKit servers via memory exhaustion in remote form deserialization when experimental features are enabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"sveltekit","vendor":"svelte"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"SvelteKit (@sveltejs/kit) versions \u003e=2.49.0 and \u003c=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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SvelteKit before 2.52.2 Memory Exhaustion via Remote Form Deserialization","id":"CVE-2026-82260","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"SvelteKit before 2.52.2 CPU Exhaustion via Remote Form Deserialization","id":"CVE-2026-82261"},"packages":[{"ecosystem":"npm","fixed":["2.52.2"],"introduced":["2.49.0"],"last_affected":[],"package":"@sveltejs/kit","purl":null,"source":"GHSA-vrhm-gvg7-fpcf"},{"ecosystem":"npm","fixed":["2.52.2"],"introduced":["2.49.0"],"last_affected":[],"package":"@sveltejs/kit","purl":"pkg:npm/%40sveltejs/kit","source":"GHSA-vrhm-gvg7-fpcf"}],"prev":{"headline":"SvelteKit 2.49.0 before 2.53.3 Denial of Service via form","id":"CVE-2026-82259"},"products":["kit"],"published":"2026-08-28","related":[{"cvss_score":8.8,"headline":"SvelteKit framework has Insufficient CSRF protection for CORS requests","id":"CVE-2023-29008","kev_date_added":null,"published":"2023-04-06"},{"cvss_score":8.8,"headline":"SvelteKit has Insufficient Cross-Site Request Forgery Protection","id":"CVE-2023-29003","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":8.7,"headline":"SvelteKit 2.49.0 before 2.53.3 Denial of Service via form","id":"CVE-2026-82259","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.7,"headline":"SvelteKit before 2.52.2 CPU Exhaustion via Remote Form Deserialization","id":"CVE-2026-82261","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":6.9,"headline":"SvelteKit before 2.69.1 Denial of Service via Remote Form","id":"CVE-2026-82256","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":5.9,"headline":"SvelteKit 2.38.0 before 2.60.1 Cross-User Data Disclosure via query.batch","id":"CVE-2026-82258","kev_date_added":null,"published":"2026-08-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["sveltejs"]},"summary":"Attackers can crash SvelteKit servers via memory exhaustion in remote form deserialization when experimental features are enabled.","url":"https://insights.sbomify.com/CVE-2026-82260/"}