Skip to main content
VulnerabilityPublished

CVE-2026-27902: sveltejs svelte · Cross-site Scripting

Affects sveltejs svelteSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 5.53.5 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.53.5
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade svelte and sveltejs/svelte to 5.53.5.

Affected software

ProductAffectedFixed in
sveltejssvelteAffected
  • >=5.53.0 <5.53.5
Fixed in
  • 5.53.5
npmsveltejs/sveltepkg:npm/sveltejs/svelteOther threatsAffected
  • <5.53.5
Fixed in
  • 5.53.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade all Svelte framework instances to version 5.53.5 or later, which contains the fix for this vulnerability.
  2. Review and sanitize any custom error handling code that interacts with transformError or similar functions to ensure no untrusted input is embedded into HTML without proper escaping.
  3. Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and mitigate the impact of potential XSS attacks.
  4. Conduct thorough security testing, including automated and manual penetration testing focused on error handling and output encoding in web applications using Svelte.
  5. Educate developers on secure coding practices related to output encoding and error message handling to prevent similar vulnerabilities.
  6. Monitor application logs and user reports for suspicious activity that may indicate attempted exploitation.
  7. If immediate upgrade is not feasible, consider temporary mitigations such as sanitizing error messages at the application layer before rendering.
  8. Keep dependencies and third-party libraries up to date and subscribe to security advisories related to Svelte and associated tooling.

Description

Svelte performance oriented web framework. Prior to version 5.53.5, errors from `transformError` were not correctly escaped prior to being embedded in the HTML output, causing potential HTML injection and XSS if attacker-controlled content is returned from `transformError`. Version 5.53.5 fixes the issue.

References

Community reviews

Loading reviews…