Is astro 7.0 vulnerable?
npm · 10 releases from 7.0.0 to 7.0.9 · latest astro is 7.4.4 · checked 1 Nov 2026
Yes: 4 known advisories
Yes. astro 7.0.9, the last 7.0 release, is affected by 4 known security advisories (1 critical, 3 medium), including CVE-2026-114128, CVE-2026-84376, CVE-2026-73422. 3 more affect earlier 7.0.x releases. Upgrade to 7.3.2 or later to fix all of them.
npm install astro@7.3.2Advisories affecting astro 7.0.9
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: Reflected XSS via unescaped View Transition animation properties
- Affected
- >=2.9.0 <7.1.0
- Fixed in
- 7.1.0
Fixed within 7.0.x, affecting earlier releases
Astro: composable `astro/hono` pipeline bypasses `security.checkOrigin` when `middleware()` is absent or misordered
- Affected
- >=7.0.0 <7.0.6
- Fixed in
- 7.0.6
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
Which of your client projects are still on astro 7.0?
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.