Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Exception handling procedures
|
| Impact | The CVSS 4.0 score of 6.3 reflects a network-accessible vulnerability with low attack complexity and no privileges required, but with partial availability impact (SA:L). The attack tree parameter AT:P suggests some attack obstacles exist, likely the need to influence application logic to reach the vulnerable code path. The EPSS score is not provided, but real-world exploitation probability is moderate given that the attack requires the redirect() function to be called from the handle hook with attacker-controlled input-a pattern that may exist in many web applications but is not universal. While no CISA KEV confirmation is present in the data, the vulnerability is actionable and straightforward to exploit if the vulnerable code pattern exists. The primary risk is application availability via DoS rather than confidentiality or integrity breach. Remediation is straightforward (upgrade to 2.57.1), making this a medium-priority item for SvelteKit deployments that use server-side redirects with untrusted input. |
| Exploit ScenarioDerived | An attacker identifies a SvelteKit application that uses server-side redirects within the handle hook and accepts user input (e.g., via query parameters or POST data) that flows to the redirect location. The attacker crafts a malicious request with a location parameter containing newline characters or other HTTP-header-invalid sequences. When the application's handle hook processes this request and calls redirect() with the malicious input, the unhandled TypeError crashes the request handler, resulting in a denial of service. No complex authentication is required; the attack succeeds through a simple HTTP request with crafted input. No public exploit code is referenced in the available data, but the vulnerability is trivial to exploit once a vulnerable code pattern is identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 10, 2026
SvelteKit versions prior to 2.57.1 are vulnerable to denial of service when the redirect() function is called from the handle server hook with HTTP header-invalid characters in the location parameter. An unauthenticated remote attacker can trigger an unhandled TypeError by supplying unsanitized user input to the redirect location, potentially causing application crashes on certain platforms. The vulnerability is fixed in version 2.57.1.
RemediationAI
Upgrade SvelteKit to version 2.57.1 or later, which contains the fix for HTTP header validation in the redirect() function. The patch is available in the official release at https://github.com/sveltejs/kit/releases/tag/@sveltejs/kit@2.57.1 and was implemented via commit 10d7b44425c3d9da642eecce373d0c6ef83b4fcd. Applications should update their SvelteKit dependency to the patched version immediately. Until patching is possible, organizations should implement input validation at the application level to sanitize user input before passing it to the redirect() function, specifically removing or encoding characters that are invalid in HTTP headers (such as CR, LF, and other control characters).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in npm, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SvelteKit's redirect() function is designed to issue HTTP redirects from server-side hooks. The handle server hook is a critical middleware component that processes all incoming requests. When redirect() receives a location parameter containing characters prohibited in HTTP headers (such as newlines or other control characters), the function fails to sanitize or validate the input before constructing the HTTP response header. This causes an unhandled TypeError at runtime due to improper input validation on untrusted data flowing through a server-side redirect mechanism. The root cause is classified as CWE-755 (Improper Handling of Exceptional Conditions), indicating a failure to gracefully handle or validate exceptional input conditions. The affected product is identified via CPE cpe:2.3:a:sveltejs:kit:*:*:*:*:*:*:*:* across all versions prior to the patch.
Know when Kit gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in SvelteKit Request Handling Vulnerabilities
View all 2SvelteKit is a web development kit. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authe
Remote denial-of-service in @sveltejs/kit (versions ≤ 2.70.1) is achievable by any unauthenticated attacker who sends a
SvelteKit 2.19.0-2.49.4 has SSRF/DoS affecting applications with prerendered routes. Can be exploited to make the server
Denial of service in SvelteKit versions 2.49.0 through 2.53.2 is achievable by unauthenticated remote attackers who subm
CPU exhaustion in SvelteKit's experimental remote form deserialization endpoint allows unauthenticated remote attackers
Memory exhaustion in @sveltejs/kit versions 2.49.0 through 2.52.1 allows unauthenticated remote attackers to crash the s
SvelteKit versions 2.49.0 through 2.49.4 are vulnerable to denial-of-service attacks through the experimental form remot
Uncontrolled payload size acceptance in SvelteKit's remote form function handler allows unauthenticated remote attackers
Cross-user data disclosure in SvelteKit (npm/@sveltejs/kit versions 2.38.0 through 2.60.0) stems from a race condition i
Prototype pollution in SvelteKit's remote form functions allows network-accessible attackers to remove methods from Java
Unauthenticated remote attackers can tamper with limited plugin-controlled data in Kit (formerly ConvertKit) for WooComm
EUVD-2026-21504
GHSA-3f6h-2hrp-w5wx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB