Open Redirect in @astrojs/node (CVE-2026-59730)
Summary
Vulnerability in @astrojs/node (CVE-2026-59730). Risk of unauthorized operations or information disclosure. Exploitable via Location. Mitigation: upgrade to 11.0.2 or later.
Original description
The description as published by the source.
Astro is a web framework for content-driven websites. In versions 8.1.0 through 11.0.1, when trailingSlash: 'always' is 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 for exploitation: trailingSlash: 'always' must be set (non-default; the default is 'ignore'), the request path must not have a file extension in its final segment, and an attacker must deliver the crafted link to a user. This issue has been fixed in version 11.0.2.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59730 has been found in @astrojs/node.
Attackers can target a specific entry point like Location over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @astrojs/node to 11.0.2 or later.
If unsure, ask your IT team or search "@astrojs/node CVE-2026-59730" on the vendor's site.
CVE-2026-59730 (@astrojs/node) — CWE-601
Attack surface: Location
Patched: 11.0.2 — apply immediately
Workaround: Use the default trailingSlash: 'ignore' setting, which does not issue trailing-slash redirects in the static file handler.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) exists in @astrojs/node. Attackers reach the vulnerable code path via Location.
Check the vendor advisory for the affected versions of @astrojs/node. Attack surface: Location.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 11.0.2.
Workaround: Use the default trailingSlash: 'ignore' setting, which does not issue trailing-slash redirects in the static file handler.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@astrojs/node' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@astrojs/node' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@astrojs/nodeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Use the default `trailingSlash: 'ignore'` setting, which does not issue trailing-slash redirects in the static file handler.パッチが適用されるまでの応急処置として、Use the default
trailingSlash: 'ignore'setting, which does not issue trailing-slash redirects in the static file handler. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade @astrojs/node to 11.0.2ステージング環境で 11.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com