Repository navigation
Update dependency @astrojs/node to v11.1.3 [SECURITY] - #56
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/npm-astrojs-node-vulnerability
branch
from
November 3, 2026 15:27
f1681d3 to
59250ec
Compare
ecv
previously approved these changes
Nov 3, 2026
ecv
left a comment
Contributor
There was a problem hiding this comment.
@astrojs/node security patch, lockfile only; checks green.
ecv
enabled auto-merge
November 3, 2026 20:12
renovate
Bot
force-pushed
the
renovate/npm-astrojs-node-vulnerability
branch
from
November 3, 2026 20:27
59250ec to
a156fbd
Compare
ecv
approved these changes
Nov 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
11.0.3→11.1.3Astro: Malformed port in the Host header can crash the Node adapter
CVE-2026-102984 / GHSA-qh8j-hqjv-7m4x
More information
Details
Summary
In the Astro Node adapter, a request whose
Hostheader contains a malformed port (for exampleexample.com:65536orexample.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 uncaughtTypeError: Invalid URLwhile the request was being built, before any route ran.Impact
The effect depends on the adapter configuration:
standalone): the request returns500 Internal Server Errorand the server continues running.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
Hostheader, and many proxies and CDNs reject malformed hosts before they reach the origin.Affected versions
@astrojs/node<= 11.1.2.Patches
Fixed in
@astrojs/node11.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 singlehostname:portpair are also rejected during host validation.Workarounds
Upgrade to
@astrojs/node11.1.3 or later. Deployments that terminate malformedHostheaders at a reverse proxy or CDN are not reachable through this path.Credits
Reported by @Celggar.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Astro: Malformed port in the Host header can crash the Node adapter
CVE-2026-102984 / GHSA-qh8j-hqjv-7m4x
More information
Details
Summary
In the Astro Node adapter, a request whose
Hostheader contains a malformed port (for exampleexample.com:65536orexample.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 uncaughtTypeError: Invalid URLwhile the request was being built, before any route ran.Impact
The effect depends on the adapter configuration:
standalone): the request returns500 Internal Server Errorand the server continues running.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
Hostheader, and many proxies and CDNs reject malformed hosts before they reach the origin.Affected versions
@astrojs/node<= 11.1.2.Patches
Fixed in
@astrojs/node11.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 singlehostname:portpair are also rejected during host validation.Workarounds
Upgrade to
@astrojs/node11.1.3 or later. Deployments that terminate malformedHostheaders at a reverse proxy or CDN are not reachable through this path.Credits
Reported by @Celggar.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
withastro/astro (@astrojs/node)
v11.1.3Compare Source
Patch Changes
#17636
51723b1Thanks @matthewp! - Updates the adapter to wait for the configured log destination through Astro's newapp.getLogger()API. This release requires Astro 7.2.1 or later.Updated dependencies [
8c193f6]:v11.1.2Compare Source
Patch Changes
c1cf110Thanks @tianrking! - Return a 404 instead of a 500 for unknown parameters that match a prerendered dynamic endpoint.v11.1.1Compare Source
Patch Changes
7da442b]:v11.1.0Compare Source
Minor Changes
90c98aeThanks @adamchal! - Whensession: falseis set inastro.config, the adapter no longer auto-wires the filesystem session driver. Combined with the matchingastrochange, this lets the session runtime tree-shake out of the server bundle.Patch Changes
004fb0aThanks @dmgawel! - Fixes middleware mode routing when a prerendered dynamic route sorts before an on-demand fallbackConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.