CVE-2026-40074: SvelteKit's invalidated redirect in handle hook causes Denial-of-Service

Published Apr 10, 2026
·
Updated

redirect, when called from inside the handle server hook with a location parameter containing characters that are invalid in a HTTP header, will cause an unhandled TypeError. This could result in DoS on some platforms, especially if the location passed to redirect contains unsanitized user input.

Other sources

SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to 2.57.1, redirect, when called from inside the handle server hook with a location parameter containing characters that are invalid in a HTTP header, will cause an unhandled TypeError. This could result in DoS on some platforms, especially if the location passed to redirect contains unsanitized user input. This vulnerability is fixed in 2.57.1.

MITRE

Affected Software

2 affected componentsFixes available
npm/@sveltejs/kit<=2.57.0
2.57.1
svelte Kit Node.js<2.57.1

Event History

Apr 10, 2026
CVE Published
via MITRE·04:26 PM
Data Sourced
via MITRE·04:26 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
RemedyAffected Software
Advisory Published
via GitHub·05:32 PM
Data Sourced
via GitHub·05:32 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-40074?

CVE-2026-40074 has a severity rating that indicates it could lead to a Denial-of-Service vulnerability under certain conditions.

2

How do I fix CVE-2026-40074?

To fix CVE-2026-40074, upgrade to version 2.57.1 or later of the @sveltejs/kit package.

3

What platforms are affected by CVE-2026-40074?

CVE-2026-40074 may affect various platforms running vulnerable versions of the @sveltejs/kit package.

4

What causes the Denial-of-Service vulnerability in CVE-2026-40074?

The Denial-of-Service in CVE-2026-40074 is caused by an unhandled TypeError when invalid characters are present in the location parameter of an HTTP header.

5

Is there a workaround for CVE-2026-40074 before upgrading?

Currently, the recommended action for CVE-2026-40074 is to upgrade to a patched version, as specific workarounds may not fully mitigate the risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203