Approved changes feed: RSS · Atom
cpe:2.3:a:@nuxt:schema:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | @Nuxt (8b917f2f-f83c-565a-be80-81e90be5ca8c) |
|---|---|
| Product | Schema (2217f33e-1688-584b-9708-0e4cadc0b6ba) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-128070 |
vulnerable | 2026-11-19 05:27:49.206369 |
Nuxt dev server serves files from a parent directory that contains a lockfile
MEDIUM (5.9)
Nuxt is an open-source web development framework for Vue.js. From 3.5.0 until 4.6.4, Nuxt can choose a parent directory as the default workspaceDir in either of two cases: a stray parent lockfile when the project is outside a Git repository and has no workspace file above it, or a parent pnpm or Deno settings file that does not declare packages or a workspace, including when the project is inside a Git repository. When the development server is reachable from an untrusted network, Vite permits /_nuxt/@fs/ requests beneath that widened directory, allowing unauthenticated clients to read files such as credentials and SSH keys. The issue affects the development server only; production builds and projects whose parent directories contain no qualifying files are unaffected. This issue is fixed in version 4.6.4.
Published: 2026-11-13T17:20:27.855Z
Updated: 2026-11-13T21:09:22.550Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.