CVE-2026-40074 | sveltejs SvelteKit up to 2.57.0 location exceptional condition (GHSA-3f6h-2hrp-w5wx)

VDB-356893 · CVE-2026-40074 · GHSA-3F6H-2HRP-W5WX SVELTEJS SVELTEKIT UP TO 2.57.0 LOCATION EXCEPTIONAL CONDITION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 0.44+ Summaryinfo A vulnerability was found in sveltejs SvelteKit up to 2.57.0. It has been classified as problematic. This impacts an unknown function. This manipulation of the argument location causes exceptional condition. This vulnerability appears as CVE-2026-40074. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended. Detailsinfo A vulnerability was found in sveltejs SvelteKit up to 2.57.0. It has been declared as problematic. Affected by this vulnerability is an unknown code block. The manipulation of the argument location with an unknown input leads to a exceptional condition vulnerability. The CWE definition for the vulnerability is CWE-755. The product does not handle or incorrectly handles an exceptional condition. As an impact it is known to affect availability. The summary by CVE is: 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. The advisory is shared at github.com. This vulnerability is known as CVE-2026-40074 since 04/09/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. Upgrading to version 2.57.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 10d7b44425c3d9da642eecce373d0c6ef83b4fcd is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Vendor sveltejs Name SvelteKit Version 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 2.18 2.19 2.20 2.21 2.22 2.23 2.24 2.25 2.26 2.27 2.28 2.29 2.30 2.31 2.32 2.33 2.34 2.35 2.36 2.37 2.38 2.39 2.40 2.41 2.42 2.43 2.44 2.45 2.46 2.47 2.48 2.49 2.50 2.51 2.52 2.53 2.54 2.55 2.56 2.57.0 License open-source CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.1 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Exceptional condition CWE: CWE-755 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: SvelteKit 2.57.1 Patch: 10d7b44425c3d9da642eecce373d0c6ef83b4fcd Timelineinfo 04/09/2026 CVE reserved 04/10/2026 +1 days Advisory disclosed 04/10/2026 +0 days VulDB entry created 04/10/2026 +0 days VulDB entry last update Sourcesinfo Advisory: GHSA-3f6h-2hrp-w5wx Status: Confirmed CVE: CVE-2026-40074 (🔒) GCVE (CVE): GCVE-0-2026-40074 GCVE (VulDB): GCVE-100-356893 Entryinfo Created: 04/10/2026 20:28 Changes: 04/10/2026 20:28 (70) Complete: 🔍 Cache ID: 99:7FB:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸