<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T01:42:58.228630+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-126362</id>
    <title>fkie_cve-2026-126362</title>
    <updated>2026-11-19T01:42:58.231051+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Astro is a web framework for content-driven websites. From 5.7.3 until 9.1.2, the @astrojs/svelte renderer inserted a named slot into the quoted name attribute of an astro-slot wrapper without HTML escaping. Request-controlled slot names containing a quote could terminate the attribute and inject active HTML. Exploitation required a hydrated Svelte component using a client:* directive and dynamic rendering of the attacker-chosen slot; components that did not render that slot emitted only Astro's escaped fallback content. Both server rendering and client-side hydration used the unsafe slot name. This issue is fixed in version 9.1.2.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-126362"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-f4j9-crrj-867q</id>
    <title>GHSA-f4j9-crrj-867q — Astro: Reflected XSS via unescaped slot names in @astrojs/svelte</title>
    <updated>2026-11-19T01:42:58.231172+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @astrojs/svelte</p>
<p>## Summary</p>
<p>The `@astrojs/svelte` renderer wraps slotted content passed to Svelte components in an `&lt;astro-slot&gt;` 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.</p>
<p>For example, a page that takes a slot name from the request:</p>
<p>```astro
---
import Tabs from '../components/Tabs.svelte';
const tab = Astro.url.searchParams.get('tab');
---
&lt;Tabs client:load active={tab}&gt;&lt;div slot={tab}&gt;…&lt;/div&gt;&lt;/Tabs&gt;
```</p>
<p>rendered with a Svelte 5 component that renders its snippets by name:</p>
<p>```svelte
&lt;script&gt;
	let { active, ...snippets } = $props();
&lt;/script&gt;
{@render snippets[active]?.()}
```</p>
<p>would output a `tab` value such as `x"&gt;&lt;img src=x onerror=alert(1)&gt;` as live HTML.</p>
<p>## Impact</p>
<p>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:</p>
<p>- The page passes request-controlled input (such as a query parameter) as a slot name.
- The Svelte component is hydrated with a `client:*` directive. For non-hydrated components the slot wrapper is removed from the output, together with its `name` attribute.
- The Svelte component renders the attacker-chosen slot, which in practice means a Svelte 5 component that renders snippets by a dynamic name. Components that never render the slot only output Astro's already escaped fallback template.</p>
<p>This is the `@…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-f4j9-crrj-867q"/>
  </entry>
</feed>
