CVE-2026-102984: Astro: Malformed port in the Host header can crash the Node adapter
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.
Published Sep 30, 2026
Affected packages
@astrojs/node
- Ecosystem
- npm
- Affected
- <= 11.1.2
- Fixed in
- 11.1.3
- Check
npm ls @astrojs/node
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 returns500 Internal Server Errorand the server continues running. - With the opt-in
staticHeaders: trueoption: the throw reaches a synchronous HTTP handler that does not catch it, becoming anuncaughtExceptionthat 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.
Credited to Celggar.
References
- https://github.com/withastro/astro/security/advisories/GHSA-qh8j-hqjv-7m4x
- https://nvd.nist.gov/vuln/detail/CVE-2026-102984
- https://github.com/withastro/astro/pull/17572
- https://github.com/withastro/astro/commit/2066f39c60707a100531b4ef4bb5dab8feafa7f2
- https://github.com/withastro/astro/releases/tag/@astrojs/[email protected]
- https://github.com/advisories/GHSA-qh8j-hqjv-7m4x
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-126364
Astro: Image endpoint in @astrojs/node can read files from a case-variant sibling of the output directory on case-sensitive filesystems
medium6.3No fixNov 13, 2026CVE-2026-59730
@astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect
low2.1Jul 20, 2026CVE-2026-41322
Astro: Cache Poisoning due to incorrect error handling when if-match header is malformed
medium5.3Apr 23, 2026CVE-2026-29772
Astro: Memory exhaustion DoS due to missing request body size limit in Server Islands
medium5.9Mar 24, 2026CVE-2026-27729
Astro has memory exhaustion DoS due to missing request body size limit in Server Actions
medium5.9Feb 25, 2026CVE-2026-27829
Astro is vulnerable to SSRF due to missing allowlist enforcement in remote image inferSize
medium6.5Feb 25, 2026
