VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

astro: vulnerability history, versions and safety

astro is a package in the npm ecosystem. Vulert records 30 vulnerabilities for it across 120 releases, from Oct 2024 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
30 vulnerabilities recorded C2 H6 M16 L6
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
24 in the last 12 months

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all astro vulnerabilities

Vulert verdict on astro 7.4.2 i

Updated on 23 Oct 2026

Careful: 7.4.2 was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

The current release contains malicious code, which caps this score.

What to do: Do not resolve 7.4.2 as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 7.4.2 — affected i
  • Vulnerabilities on record 30 over 2 years · 24 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Depended on by 145 packages i
  • Stars 63,299 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for astro, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.4.2 21 Oct 2026 C1 malicious MIT No Details →
7.4.1 19 Oct 2026 C1 malicious MIT No Details →
7.4.0 15 Oct 2026 C1 malicious MIT No Details →
7.3.8 08 Oct 2026 C1 malicious MIT No Details →
7.3.7 07 Oct 2026 C1 malicious MIT No Details →
7.3.6 06 Oct 2026 C1 malicious MIT No Details →
7.4.0-beta.1 02 Oct 2026 C1 malicious MIT No Details →
7.4.0-beta.0 01 Oct 2026 C1 malicious MIT No Details →
7.3.5 24 Sep 2026 C1 malicious MIT No Details →
7.3.4 22 Sep 2026 C1 malicious MIT No Details →
7.3.3 16 Sep 2026 C1 malicious MIT No Details →
7.3.2 08 Sep 2026 C1 L1 malicious MIT No Details →
7.3.1 03 Sep 2026 C1 M1 L1 malicious MIT No Details →
7.3.0 03 Sep 2026 C1 M1 L1 malicious MIT No Details →
7.2.10 31 Aug 2026 C1 M1 L1 malicious MIT No Details →
7.2.9 27 Aug 2026 C1 M1 L1 malicious MIT No Details →
7.2.8 26 Aug 2026 C1 M1 L1 malicious MIT No Details →
7.2.7 25 Aug 2026 C2 M1 L1 malicious MIT No Details →
7.2.6 24 Aug 2026 C2 M1 L1 malicious MIT No Details →
7.2.5 24 Aug 2026 C2 M1 L1 malicious MIT No Details →
7.2.4 19 Aug 2026 C2 M1 L1 malicious MIT No Details →
7.2.3 18 Aug 2026 C2 M2 L1 malicious MIT No Details →
7.2.2 13 Aug 2026 C2 M2 L1 malicious MIT No Details →
7.2.1 11 Aug 2026 C2 M2 L1 malicious MIT No Details →
0.0.0-incremental-graph-hashing-20260807161014 07 Aug 2026 C2 H3 M10 L2 malicious MIT No Details →
7.2.0 06 Aug 2026 C2 M2 L1 malicious MIT No Details →
7.1.6 29 Jul 2026 C2 M2 L1 malicious MIT No Details →
7.1.5 28 Jul 2026 C2 M2 L1 malicious MIT No Details →
7.1.4 27 Jul 2026 C2 M2 L1 malicious MIT No Details →
7.1.3 20 Jul 2026 C2 M2 L1 malicious MIT No Details →
7.1.2 20 Jul 2026 C2 M2 L1 malicious MIT No Details →
7.1.1 17 Jul 2026 C2 M2 L1 malicious MIT No Details →
7.1.0 16 Jul 2026 C1 malicious MIT No Details →
7.0.9 13 Jul 2026 C2 M3 malicious MIT No Details →
7.0.8 13 Jul 2026 C2 M3 malicious MIT No Details →
7.0.7 08 Jul 2026 C2 M3 malicious MIT No Details →
7.0.6 02 Jul 2026 C2 M3 malicious MIT No Details →
7.0.5 01 Jul 2026 C2 M5 malicious MIT No Details →
7.0.4 30 Jun 2026 C2 M5 malicious MIT No Details →
7.0.3 25 Jun 2026 C2 M5 L1 malicious MIT No Details →
7.0.2 23 Jun 2026 C2 M5 L1 malicious MIT No Details →
7.0.1 23 Jun 2026 C2 M5 L1 malicious MIT No Details →
7.0.0 22 Jun 2026 C2 M5 L1 malicious MIT No Details →
7.0.0-beta.6 19 Jun 2026 C2 M4 L1 malicious MIT No Details →
7.0.0-beta.5 18 Jun 2026 C2 M4 L1 malicious MIT No Details →
6.4.8 17 Jun 2026 C2 M4 L1 malicious MIT No Details →
7.0.0-beta.4 15 Jun 2026 C2 M4 L1 malicious MIT No Details →
6.4.7 15 Jun 2026 C2 H1 M4 L1 malicious MIT No Details →
6.4.6 10 Jun 2026 C2 M4 L1 malicious MIT No Details →
7.0.0-beta.3 09 Jun 2026 C2 M4 L1 malicious MIT No Details →
6.4.5 09 Jun 2026 C2 H1 M5 L1 malicious MIT No Details →
7.0.0-alpha.2 08 Jun 2026 C2 M4 L1 malicious MIT No Details →
6.4.4 03 Jun 2026 C2 H1 M5 L1 malicious MIT No Details →
6.4.3 02 Jun 2026 C2 H1 M5 L1 malicious MIT No Details →
6.4.2 28 May 2026 C2 H1 M5 L1 malicious MIT No Details →
6.4.1 28 May 2026 C2 H1 M5 L1 malicious MIT No Details →
6.4.0 28 May 2026 C2 H1 M5 L1 malicious MIT No Details →
6.3.8 26 May 2026 C2 H1 M5 L1 malicious MIT No Details →
5.18.2 26 May 2026 C2 H2 M6 L2 malicious MIT No Details →
6.3.7 21 May 2026 C2 H1 M5 L1 malicious MIT No Details →
6.3.6 20 May 2026 C2 H1 M5 L1 malicious MIT No Details →
6.3.5 18 May 2026 C2 H1 M5 L1 malicious MIT No Details →
6.3.4 18 May 2026 C2 H1 M5 L1 malicious MIT No Details →
6.3.3 14 May 2026 C2 H1 M5 L1 malicious MIT No Details →
6.3.2 13 May 2026 C2 H2 M5 L1 malicious MIT No Details →
7.0.0-alpha.1 09 May 2026 C2 M4 L1 malicious MIT No Details →
6.3.1 07 May 2026 C2 H2 M5 L1 malicious MIT No Details →
6.3.0 07 May 2026 C2 H2 M5 L1 malicious MIT No Details →
6.2.2 04 May 2026 C2 H2 M5 L1 malicious MIT No Details →
6.2.1 30 Apr 2026 C2 H2 M5 L1 malicious MIT No Details →
7.0.0-alpha.0 30 Apr 2026 C2 M4 L1 malicious MIT No Details →
6.2.0 30 Apr 2026 C2 H2 M5 L1 malicious MIT No Details →
6.1.10 28 Apr 2026 C2 H2 M5 L1 malicious MIT No Details →
6.1.9 22 Apr 2026 C2 H2 M5 L2 malicious MIT No Details →
6.1.8 18 Apr 2026 C2 H2 M5 L2 malicious MIT No Details →
6.1.7 15 Apr 2026 C2 H2 M5 L2 malicious MIT No Details →
6.1.6 13 Apr 2026 C2 H2 M5 L2 malicious MIT No Details →
6.1.5 08 Apr 2026 C2 H2 M6 L2 malicious MIT No Details →
6.1.4 06 Apr 2026 C2 H2 M6 L2 malicious MIT No Details →
6.1.3 01 Apr 2026 C2 H2 M6 L2 malicious MIT No Details →
6.1.2 30 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.1.1 26 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.1.0 26 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.8 20 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.7 19 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.6 18 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.5 16 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.4 12 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.3 11 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.2 10 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.1 10 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
5.18.1 10 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.0 10 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.0-beta.20 06 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.0-beta.19 05 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.0-beta.18 04 Mar 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.0-beta.17 26 Feb 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.0-beta.16 26 Feb 2026 C2 H2 M6 L2 malicious MIT No Details →
5.18.0 25 Feb 2026 C2 H2 M6 L3 malicious MIT No Details →
6.0.0-beta.15 24 Feb 2026 C2 H2 M6 L2 malicious MIT No Details →
6.0.0-beta.14 19 Feb 2026 C2 H2 M6 L2 malicious — No Details →
5.17.3 18 Feb 2026 C2 H2 M6 L3 malicious — No Details →
6.0.0-beta.13 17 Feb 2026 C2 H2 M6 L2 malicious — No Details →
6.0.0-beta.12 16 Feb 2026 C2 H2 M6 L2 malicious — No Details →
6.0.0-beta.11 11 Feb 2026 C2 H2 M6 L2 malicious — No Details →
5.17.2 11 Feb 2026 C2 H2 M6 L3 malicious — No Details →
6.0.0-beta.10 09 Feb 2026 C2 H2 M6 L2 malicious — No Details →
6.0.0-beta.9 05 Feb 2026 C2 H2 M6 L2 malicious — No Details →
6.0.0-beta.8 05 Feb 2026 C2 H2 M6 L2 malicious — No Details →
6.0.0-beta.7 04 Feb 2026 C2 H2 M6 L2 malicious — No Details →
6.0.0-beta.6 30 Jan 2026 C2 H2 M6 L2 malicious — No Details →
5.17.1 29 Jan 2026 C2 H2 M6 L3 malicious — No Details →
5.17.0 29 Jan 2026 C2 H2 M6 L3 malicious — No Details →
6.0.0-beta.5 28 Jan 2026 C2 H2 M6 L2 malicious — No Details →
5.16.16 28 Jan 2026 C2 H2 M6 L3 malicious — No Details →
6.0.0-beta.4 27 Jan 2026 C2 H2 M6 L2 malicious — No Details →
6.0.0-beta.3 23 Jan 2026 C2 H2 M6 L2 malicious — No Details →
5.16.15 23 Jan 2026 C2 H2 M6 L3 malicious — No Details →
5.16.14 22 Jan 2026 C2 H2 M6 L3 malicious — No Details →
6.0.0-beta.2 22 Jan 2026 C2 H2 M6 L2 malicious — No Details →

The newest 120 of 1,389 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 3
  • 2025 11
  • 2026 16

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 24 of the 30 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for astro

The 5 most severe of 30 vulnerabilities recorded for this package

Search all 30 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Critical Remote Code Execution Vulnerability in Astro Package Due to AVIF Image Optimization 9.8 critical 7.2.8 08 Sep 2026
CVE-2026-59731: Astro 6.4.7 Authorization Bypass via Decode Iteration Limit and Rewrite Path Canonicalization Mismatch 8.2 high 6.4.8 20 Jul 2026
CVE-2024-56159: Astro Package Exposes Server Source Code via Sourcemaps 7.8 high 5.0.8 19 Dec 2024
CVE-2026-54299: Astro Package Host Header SSRF Vulnerability in Prerendered Error Pages 7.5 high 6.4.6 16 Jun 2026
CVE-2025-59837: Astro Package Image Proxy Domain Validation Bypass Leading to SSRF and Potential XSS 7.2 high 5.13.10 28 Oct 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About astro

Is astro safe to use?

Vulert records 30 vulnerabilities for astro in npm: 2 critical, 6 high, 16 medium and 6 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

What is astro's Vulert package health score?

Vulert scores astro 15/100, which reads as critical. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release contains malicious code, which caps this score.

Is the latest version of astro affected?

Yes. 7.4.2, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does astro have?

30 vulnerabilities are recorded for astro in the npm ecosystem: 2 critical, 6 high, 16 medium and 6 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new astro vulnerabilities disclosed?

24 vulnerabilities were recorded for astro in the last 12 months, and the oldest entry in this database dates to 14 Oct 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of astro are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor astro for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the astro version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.