Skip to content

← Actionable
Low, CVSS 2.7amended

Qwik City Open Redirect via fixTrailingSlash

CVE-2026-25149GHSA-92j7-wgmg-f32m

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@builder.io/qwik-city 1.19.0), 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.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L/E:U · score source
EPSS
  • CVE-2026-25149: 0.27% estimated exploitation activity in the next 30 days; percentile 19.20 (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 Description An Open Redirect (CWE-601) vulnerability in Qwik City's default request handler middleware allows a remote attacker to redirect users to arbitrary protocol-relative URLs. Successful exploitation permits attackers to craft convincing phishing links that appear to originate from the trusted domain but redirect the victim to an attacker-controlled site. This affects qwik-city before version 1.19.0. This has been patched in qwik-city version 1.19.0. Impact Qwik City automatically applies the fixTrailingSlash middleware to page routes to ensure URL consistency. This vulnerability impacts all Qwik City applications deployed to runtimes that have a catch-all path to match arbitrary domains and that do not automatically normalize URL paths (e.g. Bun). Exploitation allows an attacker to craft links that trigger a 301 redirect to arbitrary protocol-relative URLs. Browsers interpret this Location header as a protocol-relative URL, redirecting the user to attacker-controlled…

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

    Amended from ghsa record GHSA-92j7-wgmg-f32m

  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-92j7-wgmg-f32m

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

Advisory: Qwik City Open Redirect via fixTrailingSlash
IDs: CVE-2026-25149, GHSA-92j7-wgmg-f32m
Record: https://patchnext.com/advisories/cve-2026-25149 (revision 3, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @builder.io/qwik-city 1.19.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @builder.io/qwik-city: affected < 1.19.0; fixed in 1.19.0

## Suggested inspection (read-only)
- `npm ls @builder.io/qwik-city --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 @builder.io/qwik-city.
- 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-92j7-wgmg-f32m (OSV record GHSA-92j7-wgmg-f32m lists affected ranges: npm @builder.io/qwik-city >=0 <1.19.0 (fixed))
- Verified: https://github.com/advisories/GHSA-92j7-wgmg-f32m (GitHub-reviewed advisory GHSA-92j7-wgmg-f32m lists affected ranges: npm @builder.io/qwik-city >=0 <1.19.0)

Commands are suggestions: review each one before running it.

Loading voting…