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:
package.json: unstaged.package-lock.json: staged and also modified in the working tree.
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)
- Restore the root
overridesblock (owner decision first). The working-treepackage.jsondeletes the whole 37-lineoverridesblock that is inHEAD.git diff HEAD -- package.jsonshows 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 inHEADand runnpm install. The owner made this change, so ask before reverting it (docs/agents/README.mdrule 16).- Result: npm audit drops to 17 findings (16 high, 1 critical). That count comes from the staged lockfile with
HEAD’spackage.json.
- Result: npm audit drops to 17 findings (16 high, 1 critical). That count comes from the staged lockfile with
- Fix the critical finding: change
@simple-git/argv-parserfrom"<2.0.1"to"^2.0.1", or remove it.- It appears twice in
HEAD, once indevDependenciesand once inoverrides. As written,"<2.0.1"excludes the patched version. - Nothing depends on it now.
npm ls @simple-git/argv-parsershows only the root,@nuxt/devtools@3.4.4no longer depends onsimple-git(npm view @nuxt/devtools@3.4.4 dependencies.simple-gitis empty), andgit grepfinds no imports. - The cleanest fix is to delete both entries. The alternative is
"^2.0.1"in both places. - Result: 16 high, 0 critical.
- It appears twice in
- Accept and track the last 16 high findings. They come from two packages with no patched release:
braces@3.0.3andnode-forge@1.4.0. No override can fix them, because no fixed version is published. This matches the existing record indocs/dev/npm-security-overrides.md§ “Unresolved upstream advisories”. - Optional cleanup: remove
@nuxt/typescript-buildfrom rootdevDependencies.- It is a Nuxt 2 webpack module. It pulls in
ts-loaderandfork-ts-checker-webpack-plugin, which bringmicromatch,chokidar@3andbraces. git grep typescript-buildfinds it only inpackage.json.- Removing it shrinks the
bracespaths, butbracesstill arrives through@nuxt/content→micromatch.
- It is a Nuxt 2 webpack module. It pulls in
- Do not run
npm audit fix --force. Its “fixes” downgradenuxtto 4.1.3, every@nx/*package to 23.2.1,@nuxt/contentto 2.13.4 and@nuxt/test-utilsto 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 |
- These counts are npm’s: affected packages, including vulnerable parents, not distinct advisories.
- Only the working tree reports these 39 packages. Restoring the overrides removes all of them:
@istanbuljs/load-nyc-config,@jest/*,jest-*,babel-jest,babel-plugin-istanbul,argparse,js-yaml,sprintf-js,@nx/*(13 packages),nx,undici,nitro,srvx,svgo,nuxt-svgo,chokidar,unplugin-vue-components,@primevue/nuxt-module,fork-ts-checker-webpack-pluginandvitest-environment-nuxt. Source: local diff of the two audit JSON files. HEADhas two critical findings because its lockfile still holdssimple-git@3.36.0, which the staged lockfile drops.
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:
- Parents with no advisory of their own.
nuxt,@nuxt/nitro-server,@nuxt/vite-builder,@nuxt/vite-server,nitropack,listhen,globby,fast-glob,micromatch,@nuxt/content,ts-loader,@nuxt/typescript-build,@nx/nuxtand@nuxt/test-utilsare flagged only because they contain group F or G. Source: theviafield innpm audit --json. - Prod/dev labels. Prod/dev comes from comparing
npm auditwith and without--omit=dev. npm’s “prod” means reachable from somedependenciesfield. It does not mean bundled into the Lambda.
Per-group details
A. @simple-git/argv-parser: critical, dev-only, orphaned
- Advisory. Versions
< 2.0.1are affected, and 2.0.1 is patched. The unsafe-editor denylist missesVISUAL, so an attacker-influenced environment can run a binary duringgit commit --amendorgit rebase -i. Exploitation requires the consumer to forward attacker-controlled env values to Git. Source: GHSA-v5rq-49vh-5v5c. - Patched release.
npm view @simple-git/argv-parser versionsshows 2.0.1 published, and it islatest. - Why it is pinned. Commit
68705022a(#278, co-authored by the Cursor agent) added"<2.0.1"to bothdevDependenciesandoverrides. At that time@nuxt/devtoolsusedsimple-git@3.36.0, which needs@simple-git/argv-parser@^1.1.0.simple-git@4.0.2pins2.0.1, pernpm view simple-git@latest dependencies. - Nothing needs it now. The doc’s earlier warning that
simple-gitv4 removed the default export applied to the old devtools. That consumer is gone. - Fix. Delete both entries, or set both to
^2.0.1. npm itself reportsfixAvailable: {version: "2.0.1", isSemVerMajor: false}.
B. undici under nx
- Patched versions. 7.29.1 (7.x line) and 8.10.2 (8.x line) are patched for both highs:
- GHSA-rfgv-xxqx-mfg5: a WebSocket client crash when the server returns an unrequested subprotocol.
- GHSA-w293-vg96-wgc3:
BalancedPooldrops function-valued TLS options.
- The nx pin.
npm view nx@23.3.0 dependencies.undicireturns7.29.0, an exact pin.nx@latestis 23.3.0; 24.x is stillrc/canary(npm view nx versions). - Fix: an override. A semver-compatible lockfile bump cannot work because of the exact pin.
HEAD’s global"undici": "^8.10.0"moves nx onto a different major.- A narrower alternative keeps nx on 7.x:
"nx": { "undici": "^7.29.1" }. Versions 7.29.1 and 7.30.x are published (npm view undici versions). - Nested override syntax is documented in the npm
overridesdocs.
- Exposure is low. nx uses undici in the CLI/daemon, not in the deployed app. This is inferred from the dependency path; the exact call sites were not checked.
C. svgo under nuxt-svgo
- Installed versions.
nuxt-svgo@4.2.6resolves its ownsvgo@3.0.2(npm ls svgo). Every workspace (core/web,core/admin,packages/image,packages/media-nuxt) already usessvgo@3.3.5. - Patched versions. GHSA-w27v-7q3p-w38r is patched in 2.8.4, 3.3.5 and 4.1.0. The 3.x line ends at 3.3.5 (
npm view svgo versions). - Fix options.
- Override
"svgo": "^3.3.5", which was inHEAD. - Or upgrade to
nuxt-svgo@5.3.0, whose dependencies aresvgo@^4.0.1and@nuxt/kit@^4.4.4(npm view nuxt-svgo@5.3.0 dependencies). That is a major bump of the module and of SVGO, so thesvgo:options atcore/web/nuxt.config.ts:459need re-checking. The nuxt-svgo changelog was not read: unverified breaking changes.
- Override
- Exposure. These advisories need attacker-controlled SVG input. This build processes the repo’s own SVGs, an inference from the dependency path.
D. srvx under nitro alpha
- Mismatch.
nitro@3.0.1-alpha.2declaressrvx@^0.10.1(npm view nitro@3.0.1-alpha.2 dependencies). Its owncrosswswants>=0.11.5, andnpm ls srvxreportsinvalid. - Advisory.
< 0.11.13is affected: GHSA-p36q-q72m-gchr, a middleware bypass via an absolute URI in the request line. - Fix.
HEAD’s"srvx": "^0.11.15"override. The root devDependency is already^0.11.15, so"$srvx"also works per the npm docs’$reference syntax. - Build output.
.output/test/server/node_modules/srvxis 0.11.22, which is patched, in the 2026-10-19 build.
E. sprintf-js / js-yaml@3 under the Jest chain
- Unpatchable leaf.
sprintf-jslatest is 1.1.3, inside the vulnerable<=1.1.3range of GHSA-hp3w-g68c-fv3c, so it has no patch (npm view sprintf-js versions). - The fix removes it. It is only reached through
js-yaml@3→argparse@1. TheHEADoverride"js-yaml": "^4.3.1"putsjs-yaml@4, which usesargparse@2withoutsprintf-js, into@istanbuljs/load-nyc-config. - Status. The staged lockfile has
js-yaml@4.3.2, and group E disappears there. - Exposure. Dev-only (Jest coverage tooling).
F. braces: no fix exists
- No patched release. GHSA-vfj7-8cjw-p6xm covers
<= 3.0.3, patched in “None”. It is a stack-exhaustion DoS from deeply nested brace patterns.npm view braces dist-tags.latestis 3.0.3. - Exposure.
micromatch/bracesis a build-time glob dependency (Nuxt Content, Nitro’sglobby, chokidar). A search of the existing.output/{production,test}/servertrees found nobracesormicromatchpackage. The only text matches were the word “braces” in@shikijs/coreandcsso. Those builds date from 2026-08-15 and 2026-10-19, so rebuild before relying on this. - No override path. No override can fix it;
npm audit fixreportsfixAvailable: falseforbracesandchokidar.
G. node-forge: no fix exists
- No patched release. GHSA-86w9-cpqp-85rv covers
<= 1.4.0, with no patch listed. RSA PKCS#1 v1.5 signature forgery with low-exponent keys (CWE-347).npm view node-forge dist-tags.latestis 1.4.0. - Exposure. It arrives through
listhen(node_modules/listhen/dist/index.mjsimportsnode-forge), Nitro’s dev-server listener, which generates self-signed certs. It is not in the built server output (same.outputcheck as F). The app does not verify RSA signatures with it (inference: no direct dependency or import). - npm’s suggested fix is a downgrade. npm suggests
nuxt@4.1.3. Installed isnuxt@4.6.2, andlatestis 4.6.2 (npm view nuxt dist-tags).
What npm audit fix does
- Without
--force.npm audit fix --dry-run --jsonadds 1 package and removes 2: it dedupesbabel-plugin-istanbul@8.0.2. Its post-fix audit is still 56 (34 / 21 / 1). It fixes nothing. - With
--force. Its targets come from thefixAvailableentries innpm audit --json. Most are downgrades or prerelease jumps:nuxt4.6.2 → 4.1.3 (downgrade; loses the Nuxt 4.5.1+ security fixes recorded indocs/dev/npm-security-overrides.md)- all
@nx/*andnx23.3.0 → 23.2.1 (downgrade) @nuxt/content3.16.2 → 2.13.4 (major downgrade)@nuxt/test-utils4.x → 0.2.2@nuxt/typescript-build3.0.2 → 2.0.3nitro→3.0.260903-beta(prerelease jump)nuxt-svgo→ 5.3.0 (the one real upgrade)braces,chokidar,@primevue/nuxt-moduleandunplugin-vue-componentswould stay unfixed (fixAvailable: false).
Risks and what to test
After any of the steps above, run:
npm install. Watch forEOVERRIDE: the npm docs say you cannot override a direct dependency with a different spec unless you use$name.HEADalready uses$@nuxt/content,$better-sqlite3and$rolldownfor this.npm auditandnpm audit --omit=dev. Expect onlybracesandnode-forge(16 high).npm run build:libs, thennpm run build(SYS_ENV=local). Also runSYS_ENV=test npm run buildbecause of the Nitro/srvx/undici overrides and theaws_lambdapreset.npm test. This covers thejs-yamloverride in the Jest/istanbul chain and@nuxt/test-utils.npx nx run web:e2e, or the locale2e:regression. Check SVG rendering after anysvgoornuxt-svgochange.- Run an Nx command such as
npx nx show projectsto confirm the CLI works on the overriddenundici. This matters most if you keep the cross-major^8.10.0.
Specific risks:
- Cross-major undici override. The global
"undici": "^8.10.0"forcesnxonto undici 8 while nx pins 7.29.0. Prefer the nested 7.x override for nx. - Removing
@nuxt/typescript-build. It is unused in code pergit grep, but@nuxt/types@^2.18.1is also Nuxt 2-era. Check type-checking (vue-tsc) after removal. - The overrides block holds unrelated pins. It also contains
axios,@nuxt/devtools,nuxt,postcss,fast-uri,brace-expansionand others. Removing it can silently regress advisories that the current audit does not show yet.
Open questions
- Was deleting the
overridesblock from the working-treepackage.jsonintentional, for example to test whether the overrides are still needed? If yes, which pins should stay? - Should
@simple-git/argv-parserbe removed outright? It has no dependents with@nuxt/devtools@3.4.4. - Should
undicifornxstay on 7.x (nested override) instead of the global^8.10.0? - Is
@nuxt/typescript-build(and@nuxt/types) still wanted in a Nuxt 4 workspace? - Unverified:
nuxt-svgo5.x breaking changes (its changelog was not read).- The exact undici call sites inside
nx. - Whether a fresh production build bundles
node-forge,bracesormicromatch. Only existing.outputtrees were checked.