fix: refresh vulnerable dependency overrides and force vite off 8.0.10 - #231
Merged
Conversation
Bump the pnpm.overrides security block (qs, brace-expansion, vite range, add ws and @grpc/grpc-js) and add an explicit vite ^8.0.16 devDependency to the eslint-plugin package. vite was only an auto-installed peer of vitest, so the override alone did not re-resolve it; the direct edge forces it off the vulnerable 8.0.10 (now 8.1.4). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sofiachakir
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change description
pnpm.overridessecurity block in the rootpackage.json:viteoverride range moved to>=8.0.0 <=8.0.15→>=8.0.16qs→>=6.15.2,brace-expansion→>=5.0.6ws@>=8.0.0 <8.20.1→>=8.20.1and@grpc/grpc-js@>=1.14.0 <1.14.4→>=1.14.4"vite": "^8.0.16"devDependency topackages/eslint-plugin(and bumpedvitestto^4.1.10).Why the extra devDependency was needed:
vitewas present only as an auto-installed peer ofvitest/@vitest/mocker, so theoverridesentry alone did not re-resolve it — the lockfile stayed pinned to the vulnerablevite@8.0.10. Declaringviteas a direct dependency creates a real edge thatauto-install-peersresolves, forcing it to8.1.4. No8.0.10remains inpnpm-lock.yaml.Type of change
Related issues
npm-@grpc/grpc-js >= 1.14.0, < 1.14.4/CVE-2026-48069
npm-@grpc/grpc-js >= 1.14.0, < 1.14.4/CVE-2026-48068
npm-@grpc/grpc-js >= 1.14.0, < 1.14.4/CVE-2026-48068
npm-@grpc/grpc-js >= 1.14.0, < 1.14.4/CVE-2026-48069
Checklists
Development
Security
Code review
🤖 Generated with Claude Code