@astrojs/svelte
Affected
- introduced
5.7.3, fixed9.1.2(semver)
Fixed versions
9.1.2
Fix
- Fixed version
9.1.2npm install @astrojs/[email protected]
Advisory
Also known as: CVE-2026-126362
Astro: Reflected XSS via unescaped slot names in @astrojs/svelte
Summary
The @astrojs/svelte renderer wraps slotted content passed to Svelte components in an <astro-slot> element, and writes the slot name into its name attribute without HTML escaping. A slot name containing " could end the attribute and inject arbitrary HTML into the page.
For example, a page that takes a slot name from the request:
---
import Tabs from '../components/Tabs.svelte';
const tab = Astro.url.searchParams.get('tab');
---
<Tabs client:load active={tab}><div slot={tab}>…</div></Tabs>
rendered with a Svelte 5 component that renders its snippets by name:
<script>
let { active, ...snippets } = $props();
</script>
{@render snippets[active]?.()}
would output a tab value such as x"><img src=x onerror=alert(1)> as live HTML.
Impact
Reflected cross-site scripting. An attacker who gets a user to open a crafted link can run JavaScript on the site's origin, but only in applications where all of the following are true:
client:* directive. For non-hydrated components the slot wrapper is removed from the output, together with its name attribute.This is the @astrojs/svelte counterpart of GHSA-8hv8-536x-4wqp (CVE-2026-50146), which fixed the same issue in astro core. The same unescaped value was also used when hydrating the component in the browser.
Affected versions
@astrojs/svelte >= 5.7.3, <= 9.1.1.
Patches
Fixed in @astrojs/svelte 9.1.2. Slot names are now HTML-escaped in the server renderer and in the client-side hydration code.
Workarounds
Upgrade to @astrojs/svelte 9.1.2 or later. Before upgrading, do not use request-controlled input as a slot name, or map it to a fixed set of known slot names before passing it to a component.
Credits
Reported by @manus-pi.
Low Basis: The source's own band: LOW
5.7.3, fixed 9.1.2 (semver)9.1.2
9.1.2npm install @astrojs/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0