CVE-2026-42567
Undergoing Analysis Undergoing Analysis - In Progress
ReDoS Vulnerability in Svelte Framework

Publication date: 2026-06-09

Last updated on: 2026-06-09

Assigner: GitHub, Inc.

Description
Svelte is a performance oriented web framework. From version 5.51.5 to before version 5.55.7, an internal regex in the Svelte runtime can take exponential time to test in <svelte:element this={tag}></svelte:element>. This issue has been patched in version 5.55.7.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-09
Last Modified
2026-06-09
Generated
2026-06-10
AI Q&A
2026-06-09
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
sveltejs svelte From 5.51.5 (inc) to 5.55.7 (exc)
svelte svelte to 5.55.7 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1333 The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-42567 is a Regular Expression Denial of Service (ReDoS) vulnerability in the Svelte web framework affecting versions 5.51.5 to 5.55.6.

The issue arises from an internal regular expression used in the `<svelte:element>` tag validation that can take exponential time to process when handling tags of unconstrained length.

This means that if an attacker can supply very long or specially crafted tag names, the regex evaluation can consume excessive CPU resources, leading to a denial of service.

The vulnerability was patched in version 5.55.7.

Impact Analysis

This vulnerability can impact you by causing high availability disruption due to resource exhaustion.

If an attacker exploits the ReDoS vulnerability by providing tags of arbitrary length, the internal regex can consume excessive CPU time, potentially leading to denial of service conditions.

However, exploitation requires high privileges and specific conditions, and applications that restrict tags to a predefined list or limit tag length are not vulnerable.

Detection Guidance

This vulnerability is related to a Regular Expression Denial of Service (ReDoS) in the Svelte framework versions 5.51.5 to 5.55.6, specifically in the <svelte:element> tag validation. Detection involves identifying if your system is running a vulnerable version of Svelte and if your application allows tags of arbitrary length that could trigger the exponential regex processing.

To detect the vulnerability on your system, you should first check the installed Svelte version. For example, if you use npm, you can run the following command in your project directory:

  • npm list svelte

If the version is between 5.51.5 and 5.55.6 (inclusive), your system is potentially vulnerable.

Additionally, you can audit your codebase to check if <svelte:element> tags are used with unconstrained or arbitrary-length tag names, which are required to exploit this vulnerability.

There are no specific network detection commands or signatures mentioned for this vulnerability, as it is a runtime regex issue triggered by specific input patterns within the application.

Mitigation Strategies

The primary mitigation step is to upgrade the Svelte framework to version 5.55.7 or later, where this vulnerability has been patched.

If upgrading immediately is not possible, you should restrict the use of <svelte:element> tags to a predefined list of allowed tags or ensure that tag names are trimmed and constrained in length to prevent triggering the vulnerable regex.

Additionally, review your application for any usage patterns that allow arbitrary-length tag names and modify them to enforce length limits or whitelist tags.

Compliance Impact

The vulnerability CVE-2026-42567 is a Regular Expression Denial of Service (ReDoS) issue that primarily impacts the availability of applications using affected versions of the Svelte framework. It does not directly involve unauthorized access to personal data or confidentiality breaches.

Since the main impact is on availability through resource exhaustion, compliance concerns with standards like GDPR or HIPAA would relate to ensuring system availability and resilience. However, there is no explicit information indicating that this vulnerability leads to data breaches or privacy violations that would directly affect compliance with these regulations.

Applications that rely on Svelte versions prior to 5.55.7 and do not restrict tag lengths may be at risk of denial of service, which could indirectly affect compliance if system downtime impacts the ability to protect or process regulated data properly.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-42567. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart