{"answers":{"affected":"2 open source packages ship an affected version, including @astrojs/node.","exploited":"There is no known exploitation of CVE-2026-59730 in the wild and no public exploit code.","fix":"Upgrade @astrojs/node to 11.0.2 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-59730 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-59730 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @astrojs/node (npm): affected from 8.1.0; fixed in 11.0.2\n- @astrojs/node (npm): affected from 8.1.0; fixed in 11.0.2\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59730/ (Markdown: https://insights.sbomify.com/CVE-2026-59730/index.md)","id":"CVE-2026-59730","markdown":"https://insights.sbomify.com/CVE-2026-59730/index.md","name":"CVE-2026-59730","record":{"aliases":["GHSA-r557-wffq-wvrc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Astro web framework","requires_auth":"none","summary":"Attackers can redirect users to external sites via crafted links when trailing slash redirects are enabled in the Astro Node adapter.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"@astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect","id":"CVE-2026-59730","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"open_redirect","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Astro 6.4.7 Authorization Bypass via Decode Iteration Limit and Rewrite Path Canonicalization Mismatch","id":"CVE-2026-59731"},"packages":[{"ecosystem":"npm","fixed":["11.0.2"],"introduced":["8.1.0"],"last_affected":[],"package":"@astrojs/node","purl":null,"source":"GHSA-r557-wffq-wvrc"},{"ecosystem":"npm","fixed":["11.0.2"],"introduced":["8.1.0"],"last_affected":[],"package":"@astrojs/node","purl":"pkg:npm/%40astrojs/node","source":"GHSA-r557-wffq-wvrc"}],"prev":{"headline":"Astro: XSS via unescaped spread attribute names in renderHTMLElement (incomplete fix for CVE-2026-54298)","id":"CVE-2026-59729"},"products":["astro"],"published":"2026-07-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["withastro"]},"summary":"Attackers can redirect users to external sites via crafted links when trailing slash redirects are enabled in the Astro Node adapter.","url":"https://insights.sbomify.com/CVE-2026-59730/"}