Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5amended

Nuxt dev server vite-node IPC socket is world-connectable on Linux

CVE-2026-56301GHSA-534h-c3cw-v3h9

What to do

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

    Affected
    >= 4.0.0, < 4.4.7>= 3.18.0, < 3.21.7
    Fixed in
    4.4.7, 3.21.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-56301: 0.15% estimated exploitation activity in the next 30 days; percentile 4.10 (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.

Impact When running nuxt dev on Linux (Node.js 20+, outside Docker / StackBlitz), Nuxt's internal vite-node IPC server binds to a Linux abstract-namespace Unix socket (\0nuxt-vite-node-<pid-<ts.sock). Abstract sockets have no filesystem inode and therefore no permission bits: any local UID on the host that can read /proc/net/unix can enumerate the socket and connect to it. The IPC server does not perform any peer-credential or shared-secret check before dispatching requests. The module request type passes its moduleId field straight into Vite's SSR fetchModule(), which is not gated by Vite's HTTP-layer server.fs.allow deny-list. A co-resident unprivileged local user can therefore request paths like /home/<dev/project/.env?raw or ~/.ssh/idrsa?raw and read the developer's secrets through the dev server's SSR plugin pipeline. The resolve request type additionally enables filesystem probing. This affects developers running nuxt dev on shared multi-tenant Linux hosts (lab machines, shared…

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

    Amended from ghsa record GHSA-534h-c3cw-v3h9

  2. Revision 1 · created ·

    Published from osv record GHSA-534h-c3cw-v3h9

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

Advisory: Nuxt dev server vite-node IPC socket is world-connectable on Linux
IDs: CVE-2026-56301, GHSA-534h-c3cw-v3h9
Record: https://patchnext.com/advisories/cve-2026-56301 (revision 2, source checked 26 Oct 2026, 13:02 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: nuxt 4.4.7, 3.21.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected >= 4.0.0, < 4.4.7; >= 3.18.0, < 3.21.7; fixed in 4.4.7, 3.21.7

## 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://osv.dev/vulnerability/GHSA-534h-c3cw-v3h9 (OSV record GHSA-534h-c3cw-v3h9 lists affected ranges: npm nuxt >=4.0.0 =3.18.0 <3.21.7 (fixed))
- Verified: https://github.com/advisories/GHSA-534h-c3cw-v3h9 (GitHub-reviewed advisory GHSA-534h-c3cw-v3h9 lists affected ranges: npm nuxt >=4.0.0 =3.18.0 <3.21.7)

Commands are suggestions: review each one before running it.

Loading voting…