ZDF
Sign inSign up

Vulnerabilities

Security fix · GHSA-w7gw-66vg-99gq

from can return a different param from the one h3 matched when the path contains

Published Oct 16, 2026 · catalog updated Oct 29, 2026 · from can return a

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-w7gw-66vg-99gq. A missing EPSS score is not a low risk. Compare from can return a with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (from can return a).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Low3.7
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
npm @nuxt/nitro-server · npm nuxt

## Impact and from return the route params that h3 matched, with their original percent-encoding preserved. To do so, they line up the raw request URL with the decoded path h3 routed on. When a path segment contained an encoded question mark ( ), h3 routed on the decoded path only up to that , but the raw URL was not cut at the same point. The helpers then read params from the wrong segments, so they could return a different value from the one h3 matched in . Named ( ), unnamed and catch-all ( ) params are affected. For example, with , a request to is matched by h3 with set to , while returned . An application is affected if it uses the Nuxt helper for one decision (such as an authorization check) and h3's matched params, or another source, for another (such as selecting the resource). In that case a request can pass the check for one resource and act on another. ## Mitigating factors - Exploitation requires an application that reads the same route param from two different sources and relies on them agreeing. Applications that read params only through from , or only through / h3's helpers, are not affected. - The helpers were introduced in . Earlier releases and Nuxt 3 are not affected. ## Affected versions and . ## Patches Fixed in . The helpers now rebuild params from exactly the path h3 routed on, and check that each value decodes to the param h3 matched. If any value does not, they return h3's params unchanged, so they can only return a different encoding of h3's match, never a different value. ## Workarounds Upgrade to . If you cannot upgrade: 1. Read a route param from a single source for both the check and the lookup. 2. Alternatively, reject requests whose path contains in a server middleware. ## References - [Server imports documentation](https://nuxt.com/docs/4.x/guide/going-further/server-imports)

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @nuxt/nitro-server>= 4.6.0 < 4.6.2
  • npm nuxt>= 4.6.0 < 4.6.2

How to fix GHSA-w7gw-66vg-99gq

  • Upgrade

    GHSA-w7gw-66vg-99gq lists a fix boundary at 4.6.2. Compare the installed build with that boundary before you change production.

  • Version check

    Seen in >= 4.6.0 < 4.6.2 · 1 other packages on the advisory

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-w7gw-66vg-99gq. A missing EPSS score is not a low risk. Compare from can return a with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with >= 4.6.0 < 4.6.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-436; CWE-863: Incorrect Authorization. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Nuxt security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 16, 2026 · Maintainer security tabs

    Detected

    ## Impact and from return the route params that h3 matched, with their original percent-encoding preserved. To do so, they line up the raw request URL with the decoded path h3 routed on. When a path segment contained an encoded question mark ( ), h3 routed on the decoded path only up to that , but the raw URL was not cut at the same point. The helpers then read params from the wrong segments, so t

  2. Oct 29, 2026 · Maintainer security tabs

    Updated

    ## Impact and from return the route params that h3 matched, with their original percent-encoding preserved. To do so, they line up the raw request URL with the decoded path h3 routed on. When a path segment contained an encoded question mark ( ), h3 routed on the decoded path only up to that , but the raw URL was not cut at the same point. The helpers then read params from the wrong segments, so t

Sources

  • Maintainer security tabsVendor advisoryGHSA-w7gw-66vg-99gq

    ## Impact and from return the route params that h3 matched, with their original percent-encoding preserved. To do so, they line up the raw request URL with the decoded path h3 routed on. When a path segment contained an encoded question mark ( ), h3 routed on the decoded path only up to that , but the raw URL was not cut at the same point. The helpers then read params from the wrong segments, so t

    github.com

Freshness

Last verified in this catalog Oct 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026