Vulnerabilities in pkg:npm/@astrojs/node

PACKAGE
Advisory Identifier: GHSA-qh8j-hqjv-7m4x
Advisory Summary

CVE-2026-102984 is a HIGH malformed port vulnerability (CWE-248: Uncaught Exception) affecting Astro libraries in the npm ecosystem. The issue involves malformed port in the host header can crash the node adapter. Remediation is available by upgrading affected packages to version 11.1.3.

9 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@astrojs/node

9 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@astrojs/node. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-qh8j-hqjv-7m4x CVE-2026-102984 HIGH Astro: Malformed port in the Host header can crash the Node adapter
GHSA-r557-wffq-wvrc CVE-2026-59730 LOW @astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect
GHSA-c57f-mm3j-27q9 CVE-2026-41322 MODERATE Astro: Cache Poisoning due to incorrect error handling when if-match header is malformed
GHSA-qq67-mvv5-fw3g CVE-2026-25545 MODERATE Astro has Full-Read SSRF in error rendering via Host: header injection
GHSA-3rmj-9m5h-8fpv CVE-2026-29772 MODERATE Astro: Memory exhaustion DoS due to missing request body size limit in Server Islands
GHSA-cj9f-h6r6-4cx2 CVE-2026-27829 MODERATE Astro is vulnerable to SSRF due to missing allowlist enforcement in remote image inferSize
GHSA-jm64-8m5q-4qh8 CVE-2026-27729 MODERATE Astro has memory exhaustion DoS due to missing request body size limit in Server Actions
GHSA-xf8x-j4p2-f749 CVE-2025-55303 MODERATE Astro allows unauthorized third-party images in _image endpoint
GHSA-9x9c-ghc5-jhw9 CVE-2025-55207 MODERATE @astrojs/node's trailing slash handling causes open redirect issue

CVE-2026-102984 at a Glance

CVE Identifier CVE-2026-102984
GHSA Identifier GHSA-qh8j-hqjv-7m4x
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-248: Uncaught Exception
Affected Product Astro
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-102984

To remediate this vulnerability, upgrade all affected Astro dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@astrojs/node fixed: 11.1.3
npm install @astrojs/node@11.1.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @astrojs/node

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-102984, inspect your project dependencies using npm:

npm ls @astrojs/node

Analyze the terminal output to locate any version of Astro in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 11.1.3), your application is affected.

Note: The npm ls @astrojs/node command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-248: Uncaught Exception, where an exception is thrown from a function, but it is not caught. In Astro, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary In the Astro Node adapter, a request whose `Host` header contains a malformed port (for example `example.com:65536` or `example.com:8080:8080`) produced an invalid request URL. The fallback intended to recover from an unparseable URL reused the same malformed host, so it failed again and raised an uncaught `TypeError: Invalid URL` while the request was being built, before any route ran. ## Impact The effect depends on the adapter configuration: - Default configuration (`standalone`): the request returns `500 Internal Server Error` and the server continues running. - With the opt-in `staticHeaders: true` option: the throw reaches a synchronous HTTP handler that does not catch it, becoming an `uncaughtException` that terminates the process. This is an availability-only issue. It does not expose data or allow code execution. Triggering it requires sending a hand-crafted `Host` header, and many proxies and CDNs reject malformed hosts before they reach the origin. ## Affected versions `@astrojs/node` <= 11.1.2. ## Patches Fixed in `@astrojs/node` 11.1.3. When the incoming host cannot be parsed, the request URL now degrades to a host the server controls, so the request is handled instead of throwing. Hosts carrying more than a single `hostname:port` pair are also rejected during host validation. ## Workarounds Upgrade to `@astrojs/node` 11.1.3 or later. Deployments that terminate malformed `Host` headers at a reverse proxy or CDN are not reachable through this path. ## Credits Reported by @Celggar.

CVE-2026-102984 Affected Astro Versions

1 component(s)
Fixed Versions:
11.1.3
Product / Package Ecosystem Affected Versions Fixed Version
@astrojs/node
npm
< 11.1.3
11.1.3

References

Frequently Asked Questions

What is CVE-2026-102984?
CVE-2026-102984 is a security vulnerability in Astro involving Malformed port in the Host header can crash the Node adapter under CWE-248: Uncaught Exception.
Which Astro versions are affected?
Affected versions include releases prior to 11.1.3 across affected packages: @astrojs/node.
What version fixes CVE-2026-102984?
Upgrading to 11.1.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @astrojs/node affected?
Yes, @astrojs/node is affected in releases prior to 11.1.3. Upgrade your dependency to 11.1.3 or later.
What CWE is associated with CVE-2026-102984?
CVE-2026-102984 is classified under CWE-248: Uncaught Exception (An exception is thrown from a function, but it is not caught.).
How can I check npm dependencies for CVE-2026-102984?
Run the dependency tree command: 'npm ls @astrojs/node'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qh8j-hqjv-7m4x",
  "modified" : "2026-09-30T23:29:40Z",
  "published" : "2026-09-30T23:29:40Z",
  "aliases" : [ "CVE-2026-102984" ],
  "summary" : "Astro: Malformed port in the Host header can crash the Node adapter",
  "details" : "## Summary\n\nIn the Astro Node adapter, a request whose `Host` header contains a malformed port (for example `example.com:65536` or `example.com:8080:8080`) produced an invalid request URL. The fallback intended to recover from an unparseable URL reused the same malformed host, so it failed again and raised an uncaught `TypeError: Invalid URL` while the request was being built, before any route ran.\n\n## Impact\n\nThe effect depends on the adapter configuration:\n\n- Default configuration (`standalone`): the request returns `500 Internal Server Error` and the server continues running.\n- With the opt-in `staticHeaders: true` option: the throw reaches a synchronous HTTP handler that does not catch it, becoming an `uncaughtException` that terminates the process.\n\nThis is an availability-only issue. It does not expose data or allow code execution. Triggering it requires sending a hand-crafted `Host` header, and many proxies and CDNs reject malformed hosts before they reach the origin.\n\n## Affected versions\n\n`@astrojs/node` <= 11.1.2.\n\n## Patches\n\nFixed in `@astrojs/node` 11.1.3. When the incoming host cannot be parsed, the request URL now degrades to a host the server controls, so the request is handled instead of throwing. Hosts carrying more than a single `hostname:port` pair are also rejected during host validation.\n\n## Workarounds\n\nUpgrade to `@astrojs/node` 11.1.3 or later. Deployments that terminate malformed `Host` headers at a reverse proxy or CDN are not reachable through this path.\n\n## Credits\n\nReported by @Celggar.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@astrojs/node"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "11.1.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 11.1.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/withastro/astro/security/advisories/GHSA-qh8j-hqjv-7m4x"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-102984"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/withastro/astro/pull/17572"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/withastro/astro/commit/2066f39c60707a100531b4ef4bb5dab8feafa7f2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/withastro/astro"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/withastro/astro/releases/tag/@astrojs/node@11.1.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-248" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-30T23:29:40Z",
    "nvd_published_at" : "2026-09-30T15:22:23Z"
  }
}