How severe is GHSA-92j7-wgmg-f32m?

No CVSS score has been assigned to GHSA-92j7-wgmg-f32m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-92j7-wgmg-f32m?

GHSA-92j7-wgmg-f32m affects the following packages: @builder.io/qwik-city (npm). Ecosystems affected: npm.

How do I fix GHSA-92j7-wgmg-f32m?

Update @builder.io/qwik-city to 1.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-92j7-wgmg-f32m is resolved across your whole dependency graph.

How do I detect GHSA-92j7-wgmg-f32m in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @builder.io/qwik-city, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-92j7-wgmg-f32m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-92j7-wgmg-f32m?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-92j7-wgmg-f32m can be triaged on real exposure rather than presence alone.

Is GHSA-92j7-wgmg-f32m actively exploited in the wild?

No public exploit code has been indexed for GHSA-92j7-wgmg-f32m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-92j7-wgmg-f32m?

GHSA-92j7-wgmg-f32m has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-92j7-wgmg-f32m?

GHSA-92j7-wgmg-f32m is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-92j7-wgmg-f32m published, and has it been updated?

GHSA-92j7-wgmg-f32m was published on February 3, 2026 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-92j7-wgmg-f32m — qwik-city

Fix: QwikDev/qwik@9959eab

GHSA-92j7-wgmg-f32m is a Open Redirect vulnerability in @builder.io/qwik-city. A fix is available for @builder.io/qwik-city — see the affected versions and patch details below.

Qwik City Open Redirect via fixTrailingSlash

Also known asCVE-2026-25149

Published

Feb 3, 2026

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-92j7-wgmg-f32m.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

9other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@builder.io/qwik-citynpm

30Kdownloads / week

Description

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 domains. This can enable phishing attacks and token theft among other common open redirect exploits.

Patches

This has been patched in qwik-city version 1.19.0. Users are strongly encouraged to update to the latest available release.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@builder.io/qwik-city`	all versions	1.19.0`npm install @builder.io/qwik-city@1.19.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @builder.io/qwik-city, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @builder.io/qwik-city to 1.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-92j7-wgmg-f32m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-92j7-wgmg-f32m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-92j7-wgmg-f32m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-92j7-wgmg-f32m in your dependencies?

O3 Security finds GHSA-92j7-wgmg-f32m across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works