Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

Astro: Malformed port in the Host header can crash the Node adapter

CVE-2026-102984GHSA-qh8j-hqjv-7m4x

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@astrojs/node 11.1.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.2 · 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 · score source
EPSS
  • CVE-2026-102984: 0.36% estimated exploitation activity in the next 30 days; percentile 30.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 <=…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-qh8j-hqjv-7m4x

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-qh8j-hqjv-7m4x

  4. Revision 1 · created ·

    Published from ghsa record GHSA-qh8j-hqjv-7m4x

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102984

Advisory: Astro: Malformed port in the Host header can crash the Node adapter
IDs: CVE-2026-102984, GHSA-qh8j-hqjv-7m4x
Record: https://patchnext.com/advisories/cve-2026-102984 (revision 4, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @astrojs/node 11.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @astrojs/node: affected <= 11.1.2; fixed in 11.1.3

## Suggested inspection (read-only)
- `npm ls @astrojs/node --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @astrojs/node.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qh8j-hqjv-7m4x (GitHub-reviewed advisory GHSA-qh8j-hqjv-7m4x lists affected ranges: npm @astrojs/node >=0 <=11.1.2)
- Verified: https://osv.dev/vulnerability/GHSA-qh8j-hqjv-7m4x (OSV record GHSA-qh8j-hqjv-7m4x lists affected ranges: npm @astrojs/node >=0 <11.1.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…