Skip to main content
VulnerabilityPublished Updated

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

Affects sveltejs svelteSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 5.51.5 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 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 sveltejs svelte to 5.51.5.

Affected software

ProductAffectedFixed in
sveltejssvelteAffected
  • <5.51.5
Fixed in
  • 5.51.5

AI-suggested

To mitigate CVE-2026-27122, organizations should immediately upgrade all Svelte instances to version 5.51.5 or later, where the vulnerability is fixed by proper validation and sanitization of the tag name in SSR. Developers should audit their codebases to identify any use of <svelte:element this={tag}> in server-side rendering contexts and ensure that untrusted input is never passed directly as tag names. Implement strict input validation and sanitization on any user-controllable data used in SSR templates. Employ Content Security Policy (CSP) headers to reduce the impact of potential XSS attacks by restricting script execution sources. Monitor application logs for unusual SSR tag usage or injection attempts. Additionally, restrict access to high privilege accounts and enforce strong authentication controls to reduce the risk of insider exploitation. Regularly update dependencies and conduct security reviews of SSR implementations to prevent similar injection vulnerabilities.

Description

svelte performance oriented web framework. Prior to 5.51.5, when using <svelte:element this={tag}> in server-side rendering, the provided tag name is not validated or sanitized before being emitted into the HTML output. If the tag string contains unexpected characters, it can result in HTML injection in the SSR output. Client-side rendering is not affected. This vulnerability is fixed in 5.51.5.

References

Community reviews

Loading reviews…