Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27902: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in sveltejs svelte

0
Medium
VulnerabilityCVE-2026-27902cvecve-2026-27902cwe-79
Published: Thu Feb 26 2026 (02/26/2026, 00:58:54 UTC)
Source: CVE Database V5
Vendor/Project: sveltejs
Product: svelte

Description

CVE-2026-27902 is a medium severity cross-site scripting (XSS) vulnerability in the Svelte web framework versions 5. 53. 0 through 5. 53. 4. The issue arises because errors from the transformError function were not properly escaped before being embedded in HTML output, allowing potential injection of malicious HTML or scripts if attacker-controlled content is returned. Exploitation requires user interaction and has a high attack complexity, limiting its ease of exploitation. The vulnerability affects web applications built with vulnerable Svelte versions and can lead to client-side code execution or data theft. The issue is fixed in version 5. 53.

AI-Powered Analysis

AILast updated: 02/26/2026, 01:42:38 UTC

Technical Analysis

CVE-2026-27902 is a cross-site scripting (XSS) vulnerability classified under CWE-79 that affects the Svelte JavaScript framework, specifically versions from 5.53.0 up to but not including 5.53.5. The vulnerability stems from improper neutralization of input during web page generation: errors returned by the transformError function were not correctly escaped before being embedded into the HTML output. This flaw allows an attacker to inject malicious HTML or JavaScript code if they can influence the content returned by transformError. Since Svelte is a performance-oriented framework used for building reactive web applications, this vulnerability can be exploited when an attacker causes an error condition that includes attacker-controlled input, which then gets reflected in the rendered HTML without proper escaping. The CVSS 4.0 score is 5.3 (medium severity), reflecting that the attack vector is network-based but requires user interaction and has high attack complexity. No privileges are required, but the vulnerability scope is limited to client-side confidentiality due to the reflected XSS nature. The vulnerability was publicly disclosed on February 26, 2026, and fixed in version 5.53.5. No known exploits are currently in the wild. This vulnerability primarily impacts developers and organizations that build web applications using the affected Svelte versions, potentially exposing end users to script injection attacks that can lead to session hijacking, data theft, or defacement.

Potential Impact

The primary impact of CVE-2026-27902 is on the confidentiality and integrity of client-side data in web applications built with vulnerable Svelte versions. Successful exploitation can allow attackers to execute arbitrary JavaScript in the context of the victim's browser, potentially leading to session hijacking, theft of sensitive information such as cookies or tokens, and unauthorized actions performed on behalf of the user. While the vulnerability does not directly affect server-side systems or availability, the reputational damage and loss of user trust can be significant for organizations. The requirement for user interaction and high attack complexity somewhat limits widespread exploitation, but targeted attacks against high-value users or administrators remain a concern. Organizations relying on Svelte for frontend development may face increased risk if they do not promptly update or implement mitigations, especially those with public-facing web applications handling sensitive user data.

Mitigation Recommendations

To mitigate CVE-2026-27902, organizations should immediately upgrade all Svelte dependencies to version 5.53.5 or later, where the vulnerability is patched. Developers should audit their code to ensure that any error messages or dynamic content derived from transformError or similar functions are properly escaped or sanitized before being embedded in HTML output. Employing Content Security Policy (CSP) headers can help reduce the impact of potential XSS by restricting the execution of unauthorized scripts. Additionally, implementing strict input validation and output encoding practices throughout the application will reduce the risk of injection flaws. Security teams should monitor for unusual client-side behavior or reports of script injection. Finally, educating developers on secure coding practices and regularly updating third-party dependencies will help prevent similar vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-24T15:19:29.718Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699fa148b7ef31ef0b7796ae

Added to database: 2/26/2026, 1:26:32 AM

Last enriched: 2/26/2026, 1:42:38 AM

Last updated: 2/26/2026, 2:43:09 AM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats