CVE-2024-23641
HIGHCVE-2024-23641 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in @sveltejs/kit. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2024-23641 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Sending a GET or HEAD request with a body crashes SvelteKit
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@sveltejs/kitnpm@sveltejs/adapter-nodenpmDescription
SvelteKit is a web development kit. In SvelteKit 2, sending a GET request with a body eg {} to a built and previewed/hosted sveltekit app throws Request with GET/HEAD method cannot have body. and crashes the preview/hosting. After this happens, one must manually restart the app. TRACE requests will also cause the app to crash. Prerendered pages and SvelteKit 1 apps are not affected. @sveltejs/adapter-node versions 2.1.2, 3.0.3, and 4.0.1 and @sveltejs/kit version 2.4.3 contain a patch for this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @sveltejs/kit | ≥ 2.0.0&&< 2.4.3 | 2.4.3 |
| 📦npm | @sveltejs/adapter-node | ≥ 2.0.0&&< 2.1.2 | 2.1.2 |
| 📦npm | @sveltejs/adapter-node | ≥ 3.0.0&&< 3.0.3 | 3.0.3 |
| 📦npm | @sveltejs/adapter-node | ≥ 4.0.0&&< 4.0.1 | 4.0.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sveltejs/kit. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @sveltejs/kit to 2.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-23641 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-23641 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-23641. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-23641 in your dependencies?
O3 detects CVE-2024-23641 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.