Skip to the content.

npm audit: 56 vulnerabilities after the root overrides block was removed

Research only. Nothing was changed while writing this note. The working copy had uncommitted changes:

Runbook for the overrides themselves: docs/dev/npm-security-overrides.md.

Resolution applied (2026-10-20)

The owner removed the overrides block on purpose, to rebuild a shorter list. The rule for the rebuild: never downgrade, use the latest compatible version, and prefer bumping a direct dependency over adding an override. The research below is kept as the record of how the problem was found.

Change in root package.json Fixes
Removed @simple-git/argv-parser ("<2.0.1") from devDependencies; no override Critical GHSA-v5rq-49vh-5v5c. Nothing depends on the package.
nuxt-svgo ^4.2.6 → ^5.3.0 (latest; depends on svgo ^4.0.1) svgo 3.0.2 advisories. nuxt-svgo@4.2.6 pinned svgo@3.0.2 exactly.
nitro ^3.0.1-alpha.2 → ^3.0.260903-beta (latest; depends on srvx ^1.0.3) srvx GHSA-p36q-q72m-gchr. The alpha required srvx ^0.10.1.
Override "nx": { "undici": "^7.29.1" } undici 7.x advisories. nx@23.3.0 (the latest) pins undici@7.29.0 exactly. The override stays within the same major version.
Override "@istanbuljs/load-nyc-config": { "js-yaml": "^4.3.2" } sprintf-js GHSA-hp3w-g68c-fv3c, reached via js-yaml@3 → argparse@1. Every other consumer is already on js-yaml ^4.

All of HEAD’s other 35 overrides were dropped. npm audit with none of them reported no findings for those packages, because upstream now ships the fixed versions.

npm install did not replace the nested @istanbuljs/load-nyc-config/node_modules/js-yaml@3.15.2 entry that was already in the lockfile, so npm ls showed it as “invalid”. Removing that stale lock entry (and its nested argparse and the hoisted sprintf-js) and running npm install again fixed it.

Result: npm audit reports 18 high, 0 critical, 0 moderate, all from braces@3.0.3 and node-forge@1.4.0, which have no patched release. The count includes the packages that depend on them.

Verified locally: npm test passed (177 files, 1300 tests) and npm run build passed. Not verified: e2e, the Docker stacks, or nuxt-svgo 5 rendering SVGs at runtime. npm install also blocked install scripts for esbuild@0.25.12, 0.27.2 and 0.28.2, because allowScripts only lists esbuild@0.28.1. The build passed without them.

TL;DR: ordered actions (research, before the resolution)

  1. Restore the root overrides block (owner decision first). The working-tree package.json deletes the whole 37-line overrides block that is in HEAD. git diff HEAD -- package.json shows only that deletion, and it accounts for 39 of the 56 findings (see the evidence below). If the deletion was unintentional, put the block back as it is in HEAD and run npm install. The owner made this change, so ask before reverting it (docs/agents/README.md rule 16).
    • Result: npm audit drops to 17 findings (16 high, 1 critical). That count comes from the staged lockfile with HEAD’s package.json.
  2. Fix the critical finding: change @simple-git/argv-parser from "<2.0.1" to "^2.0.1", or remove it.
    • It appears twice in HEAD, once in devDependencies and once in overrides. As written, "<2.0.1" excludes the patched version.
    • Nothing depends on it now. npm ls @simple-git/argv-parser shows only the root, @nuxt/devtools@3.4.4 no longer depends on simple-git (npm view @nuxt/devtools@3.4.4 dependencies.simple-git is empty), and git grep finds no imports.
    • The cleanest fix is to delete both entries. The alternative is "^2.0.1" in both places.
    • Result: 16 high, 0 critical.
  3. Accept and track the last 16 high findings. They come from two packages with no patched release: braces@3.0.3 and node-forge@1.4.0. No override can fix them, because no fixed version is published. This matches the existing record in docs/dev/npm-security-overrides.md § “Unresolved upstream advisories”.
  4. Optional cleanup: remove @nuxt/typescript-build from root devDependencies.
    • It is a Nuxt 2 webpack module. It pulls in ts-loader and fork-ts-checker-webpack-plugin, which bring micromatch, chokidar@3 and braces.
    • git grep typescript-build finds it only in package.json.
    • Removing it shrinks the braces paths, but braces still arrives through @nuxt/content → micromatch.
  5. Do not run npm audit fix --force. Its “fixes” downgrade nuxt to 4.1.3, every @nx/* package to 23.2.1, @nuxt/content to 2.13.4 and @nuxt/test-utils to 0.2.2 (details below).

Commands, after the owner confirms step 1:

# 1. restore the overrides block from HEAD (manual edit; do NOT `git checkout` the file — it may hold other wanted edits)
# 2. edit package.json: delete "@simple-git/argv-parser" from devDependencies and overrides (or set both to "^2.0.1")
npm install
npm audit                      # expect 16 high, 0 critical (braces + node-forge only)
npm audit --omit=dev

Evidence: how 56 became 17

The same npm audit was run on three dependency states. Workspace package.json files and the lockfile came from git, and each run used --package-lock-only in a scratch directory.

State Total Critical High Moderate
Working tree (overrides removed), npm audit --json 56 1 21 34
Working tree, prod only, npm audit --omit=dev --json 16 0 15 1
Index: staged lockfile + HEAD package.json (overrides present) 17 1 16 0
HEAD (commit 7b5ac0e08) 20 2 18 0

Grouped advisories (working tree, 56 findings)

# Root package (installed) Severity Advisories Path Prod / dev Fix path
A @simple-git/argv-parser@2.0.0 critical GHSA-v5rq-49vh-5v5c root devDependencies "<2.0.1" (and overrides in HEAD); no dependents dev (b) set ^2.0.1 or remove; non-major per npm fixAvailable
B undici@7.29.0 high GHSA-rfgv-xxqx-mfg5, GHSA-w293-vg96-wgc3, plus 5 moderate (3wwx, pmjh, 3xpg, 2jfj, rx4f) and 3 low (r53p, 2gqq, 8436) nx@23.3.0 → undici@7.29.0 (exact pin) npm marks it prod: nx is reachable from dependencies through @nx/devkit (c) override; HEAD had "undici": "^8.10.0". Bumping nx cannot help: nx@23.3.0 pins undici exactly at 7.29.0, and 23.3.0 is latest
C svgo@3.0.2 (nested under nuxt-svgo@4.2.6) high GHSA-xpqw-6gx7-v673, GHSA-2p49-hgcm-8545, GHSA-w27v-7q3p-w38r, GHSA-4vpr-x523-8j87 (moderate) root nuxt-svgo@^4.2.6 → svgo@3.0.2 dev (c) override "svgo": "^3.3.5" (in HEAD); or (b) nuxt-svgo@^5.3.0, which depends on svgo@^4.0.1 → 4.1.0, a major bump
D srvx@0.10.1 (nested under nitro@3.0.1-alpha.2) moderate GHSA-p36q-q72m-gchr root nitro@^3.0.1-alpha.2 declares srvx@^0.10.1 dev (c) override "srvx": "^0.11.15" (in HEAD)
E sprintf-js@1.0.3 → argparse@1 → js-yaml@3.15.2 moderate GHSA-hp3w-g68c-fv3c, the cause of 20+ moderate parents (@jest/*, jest-*, @nx/*) @nx/jest@23.3.0 → @jest/reporters → @jest/transform → babel-plugin-istanbul → @istanbuljs/load-nyc-config → js-yaml@3 dev (c) override "js-yaml": "^4.3.1" (in HEAD) removes argparse@1 and sprintf-js; sprintf-js has no patch (latest 1.1.3 ≤ vulnerable range)
F braces@3.0.3 high GHSA-vfj7-8cjw-p6xm @nuxt/content@3.16.2 → micromatch@4.0.8; nuxt → nitropack → globby → fast-glob → micromatch; @nuxt/typescript-build → fork-ts-checker/ts-loader; @primevue/nuxt-module → unplugin-vue-components → chokidar@3 npm marks it prod: nuxt and @primevue/nuxt-module are in dependencies (d) no patched version; chokidar@^5 override (in HEAD) removes the chokidar paths only
G node-forge@1.4.0 high GHSA-86w9-cpqp-85rv nuxt@4.6.2 → @nuxt/nitro-server → nitropack@2.13.5 → listhen@1.10.1 → node-forge npm marks it prod; not found in built .output/*/server (d) no patched version

Notes on the table:

Per-group details

A. @simple-git/argv-parser: critical, dev-only, orphaned

B. undici under nx

C. svgo under nuxt-svgo

D. srvx under nitro alpha

E. sprintf-js / js-yaml@3 under the Jest chain

F. braces: no fix exists

G. node-forge: no fix exists

What npm audit fix does

Risks and what to test

After any of the steps above, run:

  1. npm install. Watch for EOVERRIDE: the npm docs say you cannot override a direct dependency with a different spec unless you use $name. HEAD already uses $@nuxt/content, $better-sqlite3 and $rolldown for this.
  2. npm audit and npm audit --omit=dev. Expect only braces and node-forge (16 high).
  3. npm run build:libs, then npm run build (SYS_ENV=local). Also run SYS_ENV=test npm run build because of the Nitro/srvx/undici overrides and the aws_lambda preset.
  4. npm test. This covers the js-yaml override in the Jest/istanbul chain and @nuxt/test-utils.
  5. npx nx run web:e2e, or the local e2e:regression. Check SVG rendering after any svgo or nuxt-svgo change.
  6. Run an Nx command such as npx nx show projects to confirm the CLI works on the overridden undici. This matters most if you keep the cross-major ^8.10.0.

Specific risks:

Open questions

  1. Was deleting the overrides block from the working-tree package.json intentional, for example to test whether the overrides are still needed? If yes, which pins should stay?
  2. Should @simple-git/argv-parser be removed outright? It has no dependents with @nuxt/devtools@3.4.4.
  3. Should undici for nx stay on 7.x (nested override) instead of the global ^8.10.0?
  4. Is @nuxt/typescript-build (and @nuxt/types) still wanted in a Nuxt 4 workspace?
  5. Unverified:
    • nuxt-svgo 5.x breaking changes (its changelog was not read).
    • The exact undici call sites inside nx.
    • Whether a fresh production build bundles node-forge, braces or micromatch. Only existing .output trees were checked.