{"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-40073 in the wild and no public exploit code.","fix":"Upgrade @sveltejs/kit to 2.57.1 or later.","what":"CVE-2026-40073 is a high-severity vulnerability in sveltejs kit, published on 10 Apr 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-40073 and fix it if it is affected.\n\nWhat it is: CVE-2026-40073 is a high-severity vulnerability in sveltejs kit, published on 10 Apr 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-40073 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @sveltejs/kit (npm): affected all versions; fixed in 2.57.1\n- @sveltejs/kit (npm): affected all versions; fixed in 2.57.1\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-40073/ (Markdown: https://insights.sbomify.com/CVE-2026-40073/index.md)","id":"CVE-2026-40073","markdown":"https://insights.sbomify.com/CVE-2026-40073/index.md","name":"CVE-2026-40073","record":{"aliases":["GHSA-2crg-3p73-43xp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"SvelteKit framework","requires_auth":"none","summary":"Attackers can bypass body size limits in SvelteKit applications using adapter-node, potentially causing denial of service.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kit","vendor":"svelte"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to 2.57.1, under certain circumstances, requests could bypass the BODY_SIZE_LIMIT on SvelteKit applications running with adapter-node. This bypass does not affect body size limits at other layers of the application stack, so limits enforced in the WAF, gateway, or at the platform level are unaffected. This vulnerability is fixed in 2.57.1.","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":true,"headline":"SvelteKit has a BODY_SIZE_LIMIT bypass in @sveltejs/adapter-node","id":"CVE-2026-40073","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"SvelteKit's invalidated redirect in handle hook causes Denial-of-Service","id":"CVE-2026-40074"},"packages":[{"ecosystem":"npm","fixed":["2.57.1"],"introduced":["0"],"last_affected":[],"package":"@sveltejs/kit","purl":null,"source":"GHSA-2crg-3p73-43xp"},{"ecosystem":"npm","fixed":["2.57.1"],"introduced":["0"],"last_affected":[],"package":"@sveltejs/kit","purl":"pkg:npm/%40sveltejs/kit","source":"GHSA-2crg-3p73-43xp"}],"prev":{"headline":"web3.py affected by SSRF via CCIP Read (EIP-3668) OffchainLookup URL handling","id":"CVE-2026-40072"},"products":["kit"],"published":"2026-04-10","related":[{"cvss_score":8.2,"headline":"SvelteKit has a memory amplification DoS in Remote Functions binary form deserializer","id":"CVE-2026-22803","kev_date_added":null,"published":"2026-01-15"},{"cvss_score":6.3,"headline":"SvelteKit's invalidated redirect in handle hook causes Denial-of-Service","id":"CVE-2026-40074","kev_date_added":null,"published":"2026-04-10"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-13","vendors":["sveltejs"]},"summary":"Attackers can bypass body size limits in SvelteKit applications using adapter-node, potentially causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-40073/"}