How severe is CVE-2024-23641?

CVE-2024-23641 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-23641?

CVE-2024-23641 affects the following packages: @sveltejs/kit (npm), @sveltejs/adapter-node (npm), @sveltejs/adapter-node (npm), @sveltejs/adapter-node (npm). Ecosystems affected: npm.

How do I fix CVE-2024-23641?

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.

How do I detect CVE-2024-23641 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sveltejs/kit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-23641 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2024-23641 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-23641, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-23641?

CVE-2024-23641 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-23641?

CVE-2024-23641 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-23641 published, and has it been updated?

CVE-2024-23641 was published on January 24, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

CVE-2024-23641 — @sveltejs/kit

HIGHFix: sveltejs/kit@af34142

CVE-2024-23641 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in @sveltejs/kit. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for @sveltejs/kit — see the affected versions and patch details below.

Sending a GET or HEAD request with a body crashes SvelteKit

Also known asGHSA-g5m6-hxpp-fc49

Published

Jan 24, 2024

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-23641.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

216other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@sveltejs/kitnpm

4.7Mdownloads / week

@sveltejs/adapter-nodenpm

1.5Mdownloads / week

Description

Summary

In SvelteKit 2 sending a GET request with a body eg {} to a SvelteKit app in preview or with adapter-node throws Request with GET/HEAD method cannot have body. and crashes the app.

node:internal/deps/undici/undici:6066
          throw new TypeError("Request with GET/HEAD method cannot have body.");
                ^

TypeError: Request with GET/HEAD method cannot have body.
    at new Request (node:internal/deps/undici/undici:6066:17)
    at getRequest (file:///C:/Users/admin/Desktop/reproduction/node_modules/@sveltejs/kit/src/exports/node/index.js:107:9)
    at file:///C:/Users/admin/Desktop/reproduction/node_modules/@sveltejs/kit/src/exports/vite/preview/index.js:181:26
    at call (file:///C:/Users/admin/Desktop/reproduction/node_modules/vite/dist/node/chunks/dep-9A4-l-43.js:44795:7)
    at next (file:///C:/Users/admin/Desktop/reproduction/node_modules/vite/dist/node/chunks/dep-9A4-l-43.js:44739:5)
    at file:///C:/Users/admin/Desktop/reproduction/node_modules/@sveltejs/kit/src/exports/vite/preview/index.js:172:6
    at call (file:///C:/Users/admin/Desktop/reproduction/node_modules/vite/dist/node/chunks/dep-9A4-l-43.js:44795:7)
    at next (file:///C:/Users/admin/Desktop/reproduction/node_modules/vite/dist/node/chunks/dep-9A4-l-43.js:44739:5)
    at file:///C:/Users/admin/Desktop/reproduction/node_modules/@sveltejs/kit/src/exports/vite/preview/index.js:211:27
    at call (file:///C:/Users/admin/Desktop/reproduction/node_modules/vite/dist/node/chunks/dep-9A4-l-43.js:44795:7)

Node.js v20.11.0

TRACE requests will also cause the app to crash. Prerendered pages and SvelteKit 1 apps are not affected.

PoC

First do a fresh install of SvelteKit 2 with the example app. Typescript.

npm run build
npm run preview
Go to http://localhost:4173 (works)
curl -X GET -d "{}" http://localhost:4173/bye
Application crashes and http://localhost:4173 is down

Impact

Denial of Service for apps using adapter-node

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@sveltejs/kit`	≥ 2.0.0&&< 2.4.3	2.4.3`npm install @sveltejs/kit@2.4.3`
📦npm	`@sveltejs/adapter-node`	≥ 2.0.0&&< 2.1.2	2.1.2`npm install @sveltejs/adapter-node@2.1.2`
📦npm	`@sveltejs/adapter-node`	≥ 3.0.0&&< 3.0.3	3.0.3`npm install @sveltejs/adapter-node@3.0.3`
📦npm	`@sveltejs/adapter-node`	≥ 4.0.0&&< 4.0.1	4.0.1`npm install @sveltejs/adapter-node@4.0.1`

Affected Products

2 products · 4 configurations

Application

adapter-nodesvelte

≥ 3.0.0 && < 3.0.3

1 version

4.0.0

Application

kitsvelte

≥ 2.0.0 && < 2.4.3

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

SvelteKit is a web development kit. In SvelteKit 2, sending a GET reques…

github.comNVDFeb 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sveltejs/kit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Summary In SvelteKit 2 sending a GET request with a body eg `{}` to a SvelteKit app in preview or with `adapter-node` throws `Request with GET/HEAD method cannot have body.` and crashes the app. ``` node:internal/deps/undici/undici:6066 throw new TypeError("Request with GET/HEAD method cannot have body."); ^ TypeError: Request with GET/HEAD method cannot have body. at new Request (node:internal/deps/undici/undici:6066:17) at getRequest (file:///C:/Users/admin/Desktop/reproduction/node_modules/@sveltejs/kit/src/exports/node/index.js:107:9) at file:///

O3 Security · Impact-Aware SCA

Is CVE-2024-23641 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CWE Classification

CWE-20Improper Input Validation

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jan 24, 2024

First exploit

Feb 5, 2024

Last updated

Oct 28, 2026

Identifiers

CVE-2024-23641

GHSA-g5m6-hxpp-fc49

References

Advisorygithub.com · CVE 2024 23641.json Advisorygithub.com · GHSA g5m6 hxpp fc49 Advisorynvd.nist.gov · CVE 2024 23641 Fixgithub.com · af34142631c876a7eb62ff81f71e8a3f90dafee9 Packagegithub.com · kit

Related vulnerabilities

This CVE is high severity; 1 of 8 other CVEs affecting @sveltejs/kit is rated as high or higher (top: high).

CVE-2026-114061CVE-2026-114060CVE-2026-66062GHSA-866w-xmhq-wj7xGHSA-wqjv-9729-c5q2GHSA-hgv7-v322-mmgrCVE-2026-40073CVE-2026-40074

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2024-23641 — @sveltejs/kit

Exploitation Status

Proof-of-concept exploit code exists

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Summary

PoC

Impact

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2024-23641 in your dependencies?