Skip to main content

Kit EUVDEUVD-2026-21504

| CVE-2026-40074 MEDIUM
Improper Handling of Exceptional Conditions (CWE-755)
2026-04-10 GitHub_M GHSA-3f6h-2hrp-w5wx
6.3
CVSS 4.0 · GitHub Advisory
View

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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

kit < 2.57.1

Affected Packages

npm @sveltejs/kit fix: 2.57.1
euvd kit fix: 2.57.1

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

GitHub Advisory PRIMARY 6.3 MEDIUM
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

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
Low

Lifecycle Timeline

2
Patch released
Apr 10, 2026 - 20:30 nvd
Patch available
CVE Published
Apr 10, 2026 - 16:26 nvd
MEDIUM 6.3

DescriptionGitHub 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

EPSS Score
0.0%
Top 88% exploitable
Threat Intel
1
1 source
Data Quality
5 sources
Confidence: Medium
EUVD NVD CVE.org EPSS Vulnrichment GHSA GitHub

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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 2

More in Kit

View all
CVE-2024-23641 HIGH POC
7.5 Jan 24

SvelteKit is a web development kit. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authe

CVE-2026-66062 MEDIUM POC
5.3 Aug 07

Remote denial-of-service in @sveltejs/kit (versions ≤ 2.70.1) is achievable by any unauthenticated attacker who sends a

CVE-2025-67647 CRITICAL
9.1 Jan 15

SvelteKit 2.19.0-2.49.4 has SSRF/DoS affecting applications with prerendered routes. Can be exploited to make the server

CVE-2026-82259 HIGH
8.7 Aug 28

Denial of service in SvelteKit versions 2.49.0 through 2.53.2 is achievable by unauthenticated remote attackers who subm

CVE-2026-82261 HIGH
8.7 Aug 28

CPU exhaustion in SvelteKit's experimental remote form deserialization endpoint allows unauthenticated remote attackers

CVE-2026-82260 HIGH
8.7 Aug 28

Memory exhaustion in @sveltejs/kit versions 2.49.0 through 2.52.1 allows unauthenticated remote attackers to crash the s

CVE-2026-22803 HIGH
7.5 Jan 15

SvelteKit versions 2.49.0 through 2.49.4 are vulnerable to denial-of-service attacks through the experimental form remot

CVE-2026-82256 MEDIUM
6.9 Aug 28

Uncontrolled payload size acceptance in SvelteKit's remote form function handler allows unauthenticated remote attackers

CVE-2026-82258 MEDIUM
5.9 Aug 28

Cross-user data disclosure in SvelteKit (npm/@sveltejs/kit versions 2.38.0 through 2.60.0) stems from a race condition i

CVE-2026-82257 MEDIUM
5.3 Aug 28

Prototype pollution in SvelteKit's remote form functions allows network-accessible attackers to remove methods from Java

CVE-2026-105421 MEDIUM
5.3 Oct 05

Unauthenticated remote attackers can tamper with limited plugin-controlled data in Kit (formerly ConvertKit) for WooComm

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy