Skip to content

← Actionable
Medium, CVSS 6.5amended

Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass appMiddleware on dynamic and catch-all routes

CVE-2026-114131GHSA-6gq8-jgmh-3ffp

What to do

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

  • npm nuxt

    Affected
    >= 4.0.0, < 4.4.4>= 3.11.0, < 3.21.4
    Fixed in
    4.4.4, 3.21.4

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-114131: 0.36% estimated exploitation activity in the next 30 days; percentile 30.19 (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 Nuxt compared routeRules keys against the raw request path, without decoding percent-encoding, while the router decodes parameters when it resolves a route. A request whose path is percent-encoded can therefore resolve to a page while failing to match the route rule meant to protect it, so the rule's appMiddleware never runs, including during server rendering. Impact For a page served through a dynamic or catch-all route, an attacker can percent-encode a character in the path to skip the rule: Requesting /users/%61dmin still renders app/pages/users/[id].vue with id decoded to admin, but the rule keyed /users/admin does not match, so auth does not run and the server renders and returns the gated page to an unauthenticated visitor. No privileges and no user interaction are required, and only ASCII characters are involved. Purely static ASCII routes are not affected: static segments are matched without decoding, so a request for /%61dmin does not resolve to the page registered…

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

    Amended from ghsa record GHSA-6gq8-jgmh-3ffp

  2. Revision 3 · amended ·

    Amended from osv record GHSA-6gq8-jgmh-3ffp

  3. Revision 2 · amended ·

    Amended from ghsa record GHSA-6gq8-jgmh-3ffp

  4. Revision 1 · created ·

    Published from ghsa record GHSA-6gq8-jgmh-3ffp

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

Advisory: Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routes
IDs: CVE-2026-114131, GHSA-6gq8-jgmh-3ffp
Record: https://patchnext.com/advisories/cve-2026-114131 (revision 4, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt 4.4.4, 3.21.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected >= 4.0.0, < 4.4.4; >= 3.11.0, < 3.21.4; fixed in 4.4.4, 3.21.4

## Suggested inspection (read-only)
- `npm ls nuxt --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 nuxt.
- 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://github.com/advisories/GHSA-6gq8-jgmh-3ffp (GitHub-reviewed advisory GHSA-6gq8-jgmh-3ffp lists affected ranges: npm nuxt >=4.0.0 =3.11.0 <3.21.4)
- Verified: https://osv.dev/vulnerability/GHSA-6gq8-jgmh-3ffp (OSV record GHSA-6gq8-jgmh-3ffp lists affected ranges: npm nuxt >=4.0.0 =3.11.0 <3.21.4 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…