Is astro 5.5 vulnerable?
npm · 7 releases from 5.5.0 to 5.5.6 · latest astro is 7.4.4 · checked 2 Nov 2026
Yes: 22 known advisories
Yes. astro 5.5.6, the last 5.5 release, is affected by 22 known security advisories (1 critical, 3 high, 13 medium, 5 low), including CVE-2026-54299, CVE-2026-50146, CVE-2025-64764. Upgrade to 7.3.2 or later to fix all of them.
npm install astro@7.3.2Advisories affecting astro 5.5.6
Astro: Reflected/Stored XSS via unescaped <script>/<style> tag content in JSX/MDX rendering
- Affected
- <7.3.2
- Fixed in
- 7.3.2
Astro: Remote code execution through AVIF image optimization
- Affected
- <7.2.8
- Fixed in
- 7.2.8
Astro: Authorization bypass from missing path-segment boundary check when stripping the configured base
- Affected
- <7.2.4
- Fixed in
- 7.2.4
Astro: XSS via unescaped spread attribute names in renderHTMLElement (incomplete fix for CVE-2026-54298)
- Affected
- <7.0.6
- Fixed in
- 7.0.6
Astro: Cross-site scripting via unescaped transition:* directive values on hydrated islands
- Affected
- >=3.10.0 <7.0.4
- Fixed in
- 7.0.4
Astro: Reflected XSS via unescaped View Transition animation properties
- Affected
- >=2.9.0 <7.1.0
- Fixed in
- 7.1.0
Astro: XSS via Unescaped Attribute Names in Spread Props
- Affected
- <6.4.6
- Fixed in
- 6.4.6
Astro: Host header SSRF in prerendered error page fetch
- Affected
- <6.4.6
- Fixed in
- 6.4.6
Astro: Reflected XSS via unescaped slot name
- Affected
- <6.3.3
- Fixed in
- 6.3.3
Astro: Server island encrypted parameters vulnerable to cross-component replay
- Affected
- <6.1.10
- Fixed in
- 6.1.10
Astro: XSS in define:vars via incomplete </script> tag sanitization
- Affected
- <6.1.6
- Fixed in
- 6.1.6
Astro: Remote allowlist bypass via unanchored matchPathname wildcard
- Affected
- >=2.10.10 <5.18.1
- Fixed in
- 5.18.1
Astro has an Authentication Bypass via Double URL Encoding, a bypass for CVE-2025-64765
- Affected
- <5.15.8
- Fixed in
- 5.15.8
Astro Cloudflare adapter has Stored Cross-site Scripting vulnerability in /_image endpoint
- Affected
- <5.15.9
- Fixed in
- 5.15.9
Astro's middleware authentication checks based on url.pathname can be bypassed via url encoded values
- Affected
- <5.15.8
- Fixed in
- 5.15.8
Astro vulnerable to reflected XSS via the server islands feature
- Affected
- <5.15.8
- Fixed in
- 5.15.8
Astro Development Server has Arbitrary Local File Read
- Affected
- <5.14.3
- Fixed in
- 5.14.3
Astro vulnerable to URL manipulation via headers, leading to middleware and CVE-2025-61925 bypass
- Affected
- >=2.16.0 <5.15.5
- Fixed in
- 5.15.5
Astro development server error page is vulnerable to reflected Cross-site Scripting
- Affected
- >=5.2.0 <5.15.6
- Fixed in
- 5.15.6
Astro's `X-Forwarded-Host` is reflected without validation
- Affected
- <5.14.3
- Fixed in
- 5.14.3
Astro allows unauthorized third-party images in _image endpoint
- Affected
- >=5.0.0-alpha.0 <5.13.2 · <4.16.19
- Fixed in
- 4.16.19, 5.13.2
Astros's duplicate trailing slash feature leads to an open redirection security issue
- Affected
- >=5.2.0 <5.12.8
- Fixed in
- 5.12.8
Which of your client projects are still on astro 5.5?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact astro version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other astro versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.