Skip to content

Product

npm astro vulnerabilities

31 published CVES affecting npm astro, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
31
Critical
1
High
4
Medium
20
Low
6
Unscored
0
CISA KEV
0

Latest npm astro CVEs

Newest publication first · page 1 of 2

  1. LowCVSS 2.3 EPSS 0.32%

    Astro is a web framework for content-driven websites. Prior to 7.4.5, Astro rendered a string used as a dynamic element name as raw HTML after applying an incomplete character filter. A / in the string could make an HTML parser treat the remainder as attributes, allowing untruste...

  2. LowCVSS 2.3 EPSS 0.50%

    Astro is a web framework for content-driven websites. From 7.1.0 until 7.3.3, Astro's server-side View Transition CSS generator does not keep string animation properties within their generated declarations. An application that passes attacker-controlled data into properties such...

  3. MediumCVSS 6.1 EPSS 0.23%

    Astro is a web framework. Prior to 6.4.6, the spreadAttributes function in Astro's server-side rendering pipeline iterates over object keys and passes them directly to addAttribute, which interpolates the key into the HTML output without escaping. When a developer uses the spread...

  4. MediumCVSS 6.1 EPSS 0.27%

    Astro is a web framework. Prior to 6.3.3, 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, re...

  5. MediumCVSS 5.4 EPSS 0.53% Scanner template

    Astro is a web framework. Prior to version 5.15.8, a reflected XSS vulnerability is present when the server islands feature is used in the targeted application, regardless of what was intended by the component template(s). This issue has been patched in version 5.15.8.

  6. MediumCVSS 6.5 EPSS 1.2% Scanner template

    Astro is a web framework. In Astro versions 2.16.0 up to but excluding 5.15.5 which utilizeon-demand rendering, request headers x-forwarded-proto and x-forwarded-port are insecurely used, without sanitization, to build the URL. This has several consequences, the most important of...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.