CVE-2026-27122: Svelte SSR does not validate dynamic element tag names in `<svelte:element>`
When using 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.
Published Feb 19, 2026 · Updated Feb 23, 2026
Affected packages
svelte
- Ecosystem
- npm
- Affected
- <= 5.51.4
- Fixed in
- 5.51.5
- Check
npm ls svelte
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to elliott-with-the-longest-name-on-github.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-42567
Svelte: ReDoS in `<svelte:element>` Tag Validation
medium5.9May 14, 2026CVE-2026-42573
Svelte Vulnerable to XSS via DOM Clobbering of Internal Framework State
medium5.3May 14, 2026CVE-2026-42599
Svelte SSR vulnerable to cross-site scripting via spread attributes
medium5.1May 14, 2026GHSA-f3cj-j4f6-wq85
Svelte: SSR XSS via Insecure Promise Serialization in hydratable
medium5.3May 14, 2026CVE-2026-27901
Svelte vulnerable to XSS during SSR with contenteditable `bind:innerText` and `bind:textContent`
medium5.3Feb 26, 2026CVE-2026-27902
Svelte: XSS via HTML Comment Injection in SSR Error Boundary Hydration Markers
medium5.3Feb 26, 2026
