Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5amended

Astros's duplicate trailing slash feature leads to an open redirection security issue

CVE-2025-54793GHSA-cq8c-xv66-36gw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (astro 5.12.8), 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

  • npm astro

    Affected
    >= 5.2.0, < 5.12.8
    Fixed in
    5.12.8

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.5 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:P · score source
EPSS
  • CVE-2025-54793: 0.70% estimated exploitation activity in the next 30 days; percentile 53.08 (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.

Summary There is an Open Redirection vulnerability in the trailing slash redirection logic when handling paths with double slashes. This allows an attacker to redirect users to arbitrary external domains by crafting URLs such as https://mydomain.com//malicious-site.com/. This increases the risk of phishing and other social engineering attacks. This affects Astro =5.2.0 sites that use on-demand rendering (SSR) with the Node or Cloudflare adapter. It does not affect static sites, or sites deployed to Netlify or Vercel. Background Astro performs automatic redirection to the canonical URL, either adding or removing trailing slashes according to the value of the trailingSlash configuration option. It follows the following rules: - If trailingSlash is set to "never", https://example.com/page/ will redirect to https://example.com/page - If trailingSlash is set to "always", https://example.com/page will redirect to https://example.com/page/ It also collapses multiple trailing slashes,…

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

    Amended from ghsa record GHSA-cq8c-xv66-36gw

  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-cq8c-xv66-36gw

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-2025-54793

Advisory: Astros's duplicate trailing slash feature leads to an open redirection security issue
IDs: CVE-2025-54793, GHSA-cq8c-xv66-36gw
Record: https://patchnext.com/advisories/cve-2025-54793 (revision 3, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: astro 5.12.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm astro: affected >= 5.2.0, < 5.12.8; fixed in 5.12.8

## Suggested inspection (read-only)
- `npm ls astro --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 astro.
- 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-cq8c-xv66-36gw (OSV record GHSA-cq8c-xv66-36gw lists affected ranges: npm astro >=5.2.0 <5.12.8 (fixed))
- Verified: https://github.com/advisories/GHSA-cq8c-xv66-36gw (GitHub-reviewed advisory GHSA-cq8c-xv66-36gw lists affected ranges: npm astro >=5.2.0 <5.12.8)

Commands are suggestions: review each one before running it.

Loading voting…