Quick answers
- Is CVE-2026-50146 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50146 being exploited in the wild.
- How severe is CVE-2026-50146?
- High severity, with a CVSS score of 7.1, published 22 June 2026.
- Which products and versions are affected?
- astro (npm) < 6.3.3, SEMVER:introduced=0,fixed=6.3.3.
- Is there a fix for CVE-2026-50146?
- Yes. astro (npm): upgrade to 6.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-50146 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-50146?
- Check whether you run astro (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- astro (npm): upgrade to 6.3.3 or later
npm install astro@6.3.3
Technical details
A reflected Cross-Site Scripting (XSS) vulnerability exists in Astro's Server-Side Rendering (SSR) engine. When a component utilizes a 'client:*' directive, the framework generates a 'data-astro-template' attribute. The 'key' representing the slot name is interpolated directly into this attribute without proper HTML escaping in 'packages/astro/src/runtime/server/render/component.ts'. An attacker can provide a crafted slot name (e.g., via URL parameters) containing quotes and HTML tags to break out of the attribute context and execute arbitrary JavaScript in the victim's browser. This issue is fixed in version 6.3.3 by applying HTML escaping to the slot name.
Affected products
- withastro Astro < 6.3.3
Identifiers
- CVE-2026-50146
- GHSA-8hv8-536x-4wqp
Timeline
- 2026-06-12: advisory: GitHub Security Advisory published by maintainers
- 2026-06-22: disclosed: CVE published to NVD
- 2026-06-22: patched: Fix confirmed in version 6.3.3