How severe is GHSA-2crg-3p73-43xp?

No CVSS score has been assigned to GHSA-2crg-3p73-43xp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2crg-3p73-43xp?

GHSA-2crg-3p73-43xp affects the following packages: @sveltejs/kit (npm). Ecosystems affected: npm.

How do I fix GHSA-2crg-3p73-43xp?

Update @sveltejs/kit to 2.57.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2crg-3p73-43xp is resolved across your whole dependency graph.

How do I detect GHSA-2crg-3p73-43xp in my npm dependencies?

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.

How do I mitigate GHSA-2crg-3p73-43xp if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-2crg-3p73-43xp?

O3 pinpoints whether GHSA-2crg-3p73-43xp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2crg-3p73-43xp actively exploited in the wild?

No public exploit code has been indexed for GHSA-2crg-3p73-43xp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-2crg-3p73-43xp?

GHSA-2crg-3p73-43xp is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2crg-3p73-43xp published, and has it been updated?

GHSA-2crg-3p73-43xp was published on April 10, 2026 and was last updated on April 10, 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

GHSA-2crg-3p73-43xp

Fix: sveltejs/kit@3202ed6

GHSA-2crg-3p73-43xp is a CWE-770 vulnerability in @sveltejs/kit. O3 Security confirms whether GHSA-2crg-3p73-43xp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

@sveltejs/adapter-node has a BODY_SIZE_LIMIT bypass

Also known asCVE-2026-40073

Published

Apr 10, 2026

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@sveltejs/kitnpm

2.5Mdownloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@sveltejs/kit`	all versions	2.57.1

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. 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.57.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2crg-3p73-43xp 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 GHSA-2crg-3p73-43xp 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 GHSA-2crg-3p73-43xp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-2crg-3p73-43xp in your dependencies?

O3 detects GHSA-2crg-3p73-43xp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works