Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.1amended

@astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect

CVE-2026-59730GHSA-r557-wffq-wvrc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@astrojs/node 11.0.2), 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
2.1 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N · score source
EPSS
  • CVE-2026-59730: 0.46% estimated exploitation activity in the next 30 days; percentile 39.96 (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.

Impact With trailingSlash: 'always' configured, the @astrojs/node standalone server's static file handler appends a trailing slash to request paths and issues a 301 redirect. Paths beginning with /\ (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the Location header. Because browsers treat \ as / per the WHATWG URL specification, the resulting redirect could resolve to an external host. Preconditions: - trailingSlash: 'always' must be set (non-default; the default is 'ignore') - The request path must not have a file extension in its final segment - An attacker must deliver the crafted link to a user Patches Fixed by treating backslash-prefixed paths the same as //-prefixed paths in isInternalPath(), so they are no longer rewritten with a trailing slash. Workarounds Use the default trailingSlash: 'ignore' setting, which does not issue trailing-slash redirects in the static file handler. References - WHATWG URL spec: backslash…

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

    Amended from ghsa record GHSA-r557-wffq-wvrc

  2. Revision 2 · amended ·

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

  3. Revision 1 · created ·

    Published from osv record GHSA-r557-wffq-wvrc

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-59730

Advisory: @astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect
IDs: CVE-2026-59730, GHSA-r557-wffq-wvrc
Record: https://patchnext.com/advisories/cve-2026-59730 (revision 3, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.1)
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.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @astrojs/node: affected >= 8.1.0, < 11.0.2; fixed in 11.0.2

## 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://osv.dev/vulnerability/GHSA-r557-wffq-wvrc (OSV record GHSA-r557-wffq-wvrc lists affected ranges: npm @astrojs/node >=8.1.0 <11.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-r557-wffq-wvrc (GitHub-reviewed advisory GHSA-r557-wffq-wvrc lists affected ranges: npm @astrojs/node >=8.1.0 <11.0.2)

Commands are suggestions: review each one before running it.

Loading voting…