GitHub Advisoryadvisory · npm

GHSA-8hv8-536x-4wqp Astro: Reflected XSS via unescaped slot name

HIGH Published 2026-06-16 Modified 2026-08-12 Official page ↗
Aliases
CVE-2026-50146
Ecosystem
npm
Packages
astro
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
Weaknesses
CWE-79, CWE-80
Reviewed
2026-06-16

Affected packages

• npm astro: < 6.3.3 → fixed in 6.3.3

Description

Summary When a component uses a `client:*` directive, Astro inserts named slot content into a `data-astro-template` attribute without HTML escaping the slot name allowing an attacker to break out of the attribute context and inject arbitrary HTML, resulting in reflected XSS during SSR. This is similar to GHSA-wrwg-2hg8-v723 but exploits a different injection point. Vulnerable Code `packages/astro/src/runtime/server/render/component.ts:371:376` ```ts // component.ts:371 `${children[key]}` ``` I found that key is interpolated directly into the attribute value without proper escaping. Proof of Concept For the PoC, I set up with a minimal repository with Astro 6.3.1, Node.js: v26.0.0. `astro.config.mjs` ```js import react from '@astrojs/react'; import node from '@astrojs/node'; import { defineConfig } from 'astro/config'; export default defineConfig({ output: 'server', adapter: node({ mode: 'standalone' }), integrations: [react()], }); ``` `src/pages/index.astro` ```astro --- import Wrapper from '../components/Wrapper.jsx'; const slotName = Astro.url.searchParams.get('tab') ?? 'default'; --- content ``` `src/components/Wrapper.jsx` ```jsx export default function Wrapper() { return null; } ``` Payload: ``` abc"> This will render in html. ```html content ``` Fix I suggest leveraging the existing escape function on the slot name. ```ts // component.ts:371 `${children[key]}` ``` ---

Related

Alias · CVE (1)

Weakness · CWE (2)

  • CWE-79 Improper Neutralization of Input During Web Page Generation weakness
  • CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page weakness

References