Files or Directories Accessible to External Parties Affecting @nuxt/schema package, versions >=3.5.0 <4.6.4>=3.5.0 <4.0.0


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.42% (37th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-JS-NUXTSCHEMA-22552451
  • published15 Nov 2026
  • disclosed13 Nov 2026
  • creditsuperboy-zjc

Introduced: 13 Nov 2026

NewCVE-2026-128070  (opens in a new tab)
CWE-552  (opens in a new tab)

How to fix?

Upgrade @nuxt/schema to version 4.6.4, 4.0.0 or higher.

Overview

@nuxt/schema is a Nuxt types and default configuration

Affected versions of this package are vulnerable to Files or Directories Accessible to External Parties via incorrect resolution of workspaceDir in packages/schema/src/utils/workspace-dir.ts, which can select a parent directory as the workspace root when that directory contains a stray lockfile (while the project is outside a Git repository and has no workspace file above it) or a pnpm-workspace.yaml without a packages list, or a deno.json/deno.jsonc without a workspace field. Because Vite's dev server permits /_nuxt/@fs/ requests for any path beneath workspaceDir, an unauthenticated attacker who can reach the dev server can read arbitrary files in that widened directory, including SSH keys, cloud credentials, and the Nuxt DevTools auth token.

Note: This is only exploitable when the dev server is reachable from an untrusted network (e.g. via --host, --tunnel, a published container port, or a proxy) and a parent directory contains one of the qualifying files described above; the default localhost bind and production builds are unaffected.

Workaround

Set workspaceDir explicitly in nuxt.config.ts to the project root or the real monorepo root, or remove the stray lockfile or settings file from the parent directory. Do not expose the dev server to untrusted networks. If the dev port was reachable from an untrusted network while this layout was in place, treat files in the parent directory as exposed and rotate credentials such as SSH keys and cloud tokens.

CVSS Base Scores

version 4.0
version 3.1