[DependOnMe] Critical security fix - 2 issue(s)#22
Open
dependonme-deriv wants to merge 2 commits into
Open
Conversation
Automatically regenerated by DependOnMe bot after package.json update. Branch: dependonme/bulk-fix-ea59f65e Package manager: npm
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Filespackage-lock.json
|
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
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.
Bulk Security Fix
This pull request was automatically generated by DependOnMe to fix 2 critical security issue(s).
Issues Fixed
Files Modified
package.jsonAI Summary
Fixed 2 security issues (both are the same CVE on the same package, reported twice):
vitestfrom^3.1.2to^4.1.0. The vulnerability allows arbitrary file read and execution when the Vitest UI server is listening. Fixed by upgrading to the patched version4.1.0+.What was changed and why:
vitest:^3.1.2→^4.1.0— Direct fix for CVE-2026-47429@vitest/coverage-istanbul:^3.1.2→^4.1.0— Required to match vitest major version (peer dependency alignment)@vitest/coverage-v8:^3.1.2→^4.1.0— Required to match vitest major version (peer dependency alignment)@vitest/ui:^3.1.2→^4.1.0— Required to match vitest major version (peer dependency alignment)All
@vitest/*ecosystem packages must share the same major version asvitestitself to avoid peer dependency conflicts. Failing to update them would result in npm install errors or runtime incompatibilities.vite ^6.3.4(already present) satisfies Vitest 4.x peer dependency requirements — no vite upgrade needed.package.json.Manual Steps Required:
node_modulesandpackage-lock.jsonnpm installto regenerate the lock file with the patched versions🧪 Testing Checklist:
npm installsuccessfully (no peer dependency errors)npm test— verify all tests pass under Vitest 4.xnpm run test:coverage— verify coverage reporting still worksnpm run report— verify Vitest UI (--ui) still launches correctlynpm run build— verify the library build is unaffectedThis PR was created by DependOnMe - Automated Security Issue Management