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

> Attackers can redirect users to external sites via crafted links when trailing slash redirects are enabled in the Astro Node adapter.

- **Severity:** Low 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-r557-wffq-wvrc

## What is CVE-2026-59730?

CVE-2026-59730 is a low-severity vulnerability in withastro astro, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-59730?

2 open source packages ship an affected version, including @astrojs/node.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@astrojs/node` | npm | From 8.1.0 | 11.0.2 |
| `@astrojs/node` | npm | From 8.1.0 | 11.0.2 |

## How do I fix CVE-2026-59730?

Upgrade @astrojs/node to 11.0.2 or later.

## Is CVE-2026-59730 being exploited?

There is no known exploitation of CVE-2026-59730 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59730 and fix it if it is affected.

What it is: CVE-2026-59730 is a low-severity vulnerability in withastro astro, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-59730 in the wild and no public exploit code.

Affected packages and fixed versions:
- @astrojs/node (npm): affected from 8.1.0; fixed in 11.0.2
- @astrojs/node (npm): affected from 8.1.0; fixed in 11.0.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59730/ (Markdown: https://insights.sbomify.com/CVE-2026-59730/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59730
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59730
- OSV: https://osv.dev/vulnerability/CVE-2026-59730

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59730/
Summaries are generated and may contain mistakes; the official description above is the record.