VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@astrojs/node: vulnerability history, versions and safety

@astrojs/node is a package in the npm ecosystem. Vulert records 8 vulnerabilities for it across 112 releases, from Aug 2025 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded H1 M6 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
7 in the last 12 months

Most recent disclosure 30 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @astrojs/node vulnerabilities

Vulert verdict on @astrojs/node 11.1.9 i

Updated on 23 Oct 2026

Good news: 11.1.9, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 8.

Package health score 74/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

What to do: Stay on 11.1.9 or newer. This can change: a vulnerability disclosed tomorrow can affect 11.1.9 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 11.1.9 — unaffected i
  • Vulnerabilities on record 8 over 1 year · 7 in the last year i
  • Latest disclosure 30 Sep 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 18 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 @astrojs/node, 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
11.1.9 19 Oct 2026 none MIT — Details →
11.1.8 15 Oct 2026 none MIT — Details →
11.1.7 06 Oct 2026 none MIT — Details →
11.1.7-beta.0 01 Oct 2026 none MIT — Details →
11.1.6 16 Sep 2026 none MIT — Details →
11.1.5 31 Aug 2026 none MIT — Details →
11.1.4 19 Aug 2026 none MIT — Details →
11.1.3 18 Aug 2026 none MIT — Details →
11.1.2 13 Aug 2026 H1 MIT Yes Details →
11.1.1 11 Aug 2026 H1 MIT Yes Details →
11.1.0 06 Aug 2026 H1 MIT Yes Details →
11.0.3 28 Jul 2026 H1 MIT Yes Details →
11.0.2 02 Jul 2026 H1 MIT Yes Details →
11.0.1 01 Jul 2026 H1 L1 MIT Yes Details →
11.0.0 22 Jun 2026 H1 L1 MIT Yes Details →
11.0.0-beta.2 15 Jun 2026 H1 L1 MIT Yes Details →
11.0.0-beta.1 13 Jun 2026 H1 L1 MIT Yes Details →
10.1.4 09 Jun 2026 H1 L1 MIT Yes Details →
10.1.3 02 Jun 2026 H1 L1 MIT Yes Details →
10.1.2 28 May 2026 H1 L1 MIT Yes Details →
10.1.1 13 May 2026 H1 L1 MIT Yes Details →
10.1.0 07 May 2026 H1 L1 MIT Yes Details →
11.0.0-alpha.0 30 Apr 2026 H1 L1 MIT Yes Details →
10.0.6 22 Apr 2026 H1 L1 MIT Yes Details →
10.0.5 15 Apr 2026 H1 L1 MIT Yes Details →
10.0.4 26 Mar 2026 H1 M1 L1 MIT Yes Details →
10.0.3 19 Mar 2026 H1 M1 L1 MIT Yes Details →
10.0.2 16 Mar 2026 H1 M1 L1 MIT Yes Details →
10.0.1 12 Mar 2026 H1 M1 L1 MIT Yes Details →
9.5.5 10 Mar 2026 H1 M2 L1 MIT Yes Details →
10.0.0 10 Mar 2026 H1 M1 L1 MIT Yes Details →
10.0.0-beta.9 06 Mar 2026 H1 M2 L1 MIT Yes Details →
10.0.0-beta.8 05 Mar 2026 H1 M2 L1 MIT Yes Details →
10.0.0-beta.7 04 Mar 2026 H1 M2 L1 MIT Yes Details →
10.0.0-beta.6 26 Feb 2026 H1 M2 L1 MIT Yes Details →
10.0.0-beta.5 24 Feb 2026 H1 M2 L1 MIT Yes Details →
9.5.4 18 Feb 2026 H1 M2 L1 MIT Yes Details →
10.0.0-beta.4 11 Feb 2026 H1 M2 L1 MIT Yes Details →
9.5.3 11 Feb 2026 H1 M5 L1 MIT Yes Details →
10.0.0-beta.3 09 Feb 2026 H1 M2 L1 MIT Yes Details →
10.0.0-beta.2 05 Feb 2026 H1 M2 L1 MIT Yes Details →
10.0.0-beta.1 04 Feb 2026 H1 M2 L1 MIT Yes Details →
9.5.2 16 Jan 2026 H1 M5 L1 MIT Yes Details →
10.0.0-beta.0 13 Jan 2026 H1 M2 L1 MIT Yes Details →
10.0.0-alpha.3 18 Dec 2025 H1 M2 L1 MIT Yes Details →
10.0.0-alpha.2 12 Dec 2025 H1 M2 L1 MIT Yes Details →
9.5.1 17 Nov 2025 H1 M5 L1 MIT Yes Details →
10.0.0-alpha.0 10 Nov 2025 H1 M2 L1 MIT Yes Details →
9.5.0 14 Oct 2025 H1 M5 L1 MIT Yes Details →
9.4.6 10 Oct 2025 H1 M5 L1 MIT Yes Details →
9.4.5 09 Oct 2025 H1 M5 L1 MIT Yes Details →
9.4.4 22 Sep 2025 H1 M5 L1 MIT Yes Details →
9.4.3 22 Aug 2025 H1 M5 L1 MIT Yes Details →
9.4.2 15 Aug 2025 H1 M5 L1 MIT Yes Details →
9.4.1 14 Aug 2025 H1 M5 L1 MIT Yes Details →
9.4.0 08 Aug 2025 H1 M6 L1 MIT Yes Details →
9.3.3 01 Aug 2025 H1 M6 L1 MIT Yes Details →
9.3.2 31 Jul 2025 H1 M6 L1 MIT Yes Details →
9.3.1 29 Jul 2025 H1 M6 L1 MIT Yes Details →
9.3.0 03 Jul 2025 H1 M6 L1 MIT Yes Details →
9.2.2 21 May 2025 H1 M6 L1 MIT Yes Details →
9.2.1 23 Apr 2025 H1 M6 L1 MIT Yes Details →
9.2.0 15 Apr 2025 H1 M6 L1 MIT Yes Details →
9.1.3 11 Mar 2025 H1 M6 L1 MIT Yes Details →
9.1.2 27 Feb 2025 H1 M6 L1 MIT Yes Details →
9.1.1 24 Feb 2025 H1 M6 L1 MIT Yes Details →
9.1.0 13 Feb 2025 H1 M6 L1 MIT Yes Details →
9.0.3 12 Feb 2025 H1 M6 L1 MIT Yes Details →
0.0.0-adapter-sessions-20250207124921 07 Feb 2025 H1 M4 MIT Yes Details →
9.0.2 22 Jan 2025 H1 M6 L1 MIT Yes Details →
9.0.1 13 Jan 2025 H1 M6 L1 MIT Yes Details →
9.0.0 03 Dec 2024 H1 M6 L1 MIT Yes Details →
9.0.0-beta.3 31 Oct 2024 H1 M4 L1 MIT Yes Details →
8.3.4 20 Sep 2024 H1 M4 L1 MIT Yes Details →
9.0.0-beta.2 17 Sep 2024 H1 M4 L1 MIT Yes Details →
9.0.0-alpha.1 23 Aug 2024 H1 M4 L1 MIT Yes Details →
9.0.0-alpha.0 19 Aug 2024 H1 M4 L1 MIT Yes Details →
8.3.3 14 Aug 2024 H1 M4 L1 MIT Yes Details →
0.0.0-server-islands-20240709194928 09 Jul 2024 H1 M4 MIT Yes Details →
0.0.0-server-islands-20240703133809 03 Jul 2024 H1 M4 MIT Yes Details →
8.3.2 24 Jun 2024 H1 M4 L1 MIT Yes Details →
0.0.0-server-islands-20240621194657 21 Jun 2024 H1 M4 MIT Yes Details →
8.3.1 17 Jun 2024 H1 M4 L1 MIT Yes Details →
0.0.0-experimental-container-20240613104104 13 Jun 2024 H1 M4 MIT Yes Details →
8.3.0 11 Jun 2024 H1 M4 L1 MIT Yes Details →
8.2.6 08 Jun 2024 H1 M4 L1 MIT Yes Details →
8.2.5 20 Mar 2024 H1 M4 L1 MIT Yes Details →
8.2.4 18 Mar 2024 H1 M4 L1 MIT Yes Details →
8.2.3 01 Mar 2024 H1 M4 L1 MIT Yes Details →
8.2.2 01 Mar 2024 H1 M4 L1 MIT Yes Details →
8.2.1 23 Feb 2024 H1 M4 L1 MIT Yes Details →
0.0.0-edge-nested-20240223135627 23 Feb 2024 H1 M4 MIT Yes Details →
0.0.0-edge-middleware-verification-20240205180401 05 Feb 2024 H1 M4 MIT Yes Details →
8.2.0 01 Feb 2024 H1 M4 L1 MIT Yes Details →
0.0.0-toolbar-absolute-paths-20240126155246 26 Jan 2024 H1 M4 MIT Yes Details →
8.1.0 26 Jan 2024 H1 M4 L1 MIT Yes Details →
0.0.0-isr-20240125224234 25 Jan 2024 H1 M4 MIT Yes Details →
0.0.0-node-trailing-slash-20240118204342 18 Jan 2024 H1 M4 MIT Yes Details →
8.0.0 18 Jan 2024 H1 M4 MIT Yes Details →
0.0.0-isr-20240110194136 10 Jan 2024 H1 M4 MIT Yes Details →
7.0.4 02 Jan 2024 H1 M4 — Yes Details →
7.0.3 27 Dec 2023 H1 M4 — Yes Details →
7.0.2 20 Dec 2023 H1 M4 — Yes Details →
7.0.1 11 Dec 2023 H1 M4 — Yes Details →
0.0.0-add-stable-20231208215901 08 Dec 2023 H1 M4 — Yes Details →
7.0.0 05 Dec 2023 H1 M4 — Yes Details →
7.0.0-beta.1 29 Nov 2023 H1 M4 — Yes Details →
6.1.0 28 Nov 2023 H1 M4 — Yes Details →
7.0.0-beta.0 27 Nov 2023 H1 M4 — Yes Details →
6.0.4 16 Nov 2023 H1 M4 — Yes Details →
6.0.3 05 Oct 2023 H1 M4 — Yes Details →
6.0.2 02 Oct 2023 H1 M4 — Yes Details →
6.0.1 21 Sep 2023 H1 M4 — Yes Details →
6.0.0 30 Aug 2023 H1 M4 — Yes Details →
5.3.6 23 Aug 2023 H1 M4 — Yes Details →
6.0.0-rc.1 22 Aug 2023 H1 M4 — Yes Details →
5.3.5 18 Aug 2023 H1 M4 — Yes Details →
5.3.4 15 Aug 2023 H1 M4 — Yes Details →
5.3.3 11 Aug 2023 H1 M4 — Yes Details →
6.0.0-beta.0 03 Aug 2023 H1 M4 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 7

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

03 Vulnerabilities

Recorded vulnerabilities for @astrojs/node

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-102984: @astrojs/node Malformed Host Header Causes Node Adapter Crash 8.2 high 11.1.3 30 Sep 2026
CVE-2026-25545: Astro Package Suffers from Full-Read SSRF via Host Header Injection 6.9 medium 9.5.4 23 Feb 2026
CVE-2026-27829: SSRF Vulnerability in @astrojs/node Due to Missing Allowlist Enforcement 6.5 medium 9.5.4 25 Feb 2026
CVE-2026-27729: Memory Exhaustion DoS in @astrojs/node Due to Missing Request Body Size Limit 5.9 medium 9.5.4 25 Feb 2026
CVE-2026-29772: Astro Package Memory Exhaustion DoS Due to Missing Request Body Size Limit 5.9 medium 10.0.0 24 Mar 2026

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 @astrojs/node

Is @astrojs/node safe to use?

Vulert records 8 vulnerabilities for @astrojs/node in npm: 0 critical, 1 high, 6 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @astrojs/node's Vulert package health score?

Vulert scores @astrojs/node 74/100, which reads as in good shape. 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).

Is the latest version of @astrojs/node affected?

No. 11.1.9, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @astrojs/node have?

8 vulnerabilities are recorded for @astrojs/node in the npm ecosystem: 0 critical, 1 high, 6 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @astrojs/node vulnerabilities disclosed?

7 vulnerabilities were recorded for @astrojs/node in the last 12 months, and the oldest entry in this database dates to 15 Aug 2025. 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 @astrojs/node 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.

How do I monitor @astrojs/node for upcoming vulnerabilities?

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