chore(deps): bump vitest to ^4.1.11 (GHSA-82fw-gwwq-j7x9) - #223
Merged
Merged
Conversation
GHSA-82fw-gwwq-j7x9 (moderate): Vitest path traversal / arbitrary file read via @vitest/mocker redirect mock. Fixed in 4.1.11. The advisory was published after develop's last green CI run, so the dependency audit now fails on unchanged develop. Red proven by CI run 34563284871 on the untouched dependency set; green proven locally after the bump: 'bun audit' exits clean. No source changes.
🔍 Cora AI Code ReviewReview powered by cora-code · BYOK · MIT |
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
1 participant
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.
What
web/: vitest^4.1.10→^4.1.11+ regeneratedbun.lock. No source changes.Why
GHSA-82fw-gwwq-j7x9 (moderate): Vitest path traversal / arbitrary file read via
@vitest/mockerredirect mock, fixed in 4.1.11. The advisory was published after develop's last green CI run, which is why theBun Auditcheck now fails on PRs whose dependency set is byte-identical to develop (verified before this change — including this repo's open cla-check PR #222).Testing
Bun Auditfail) on the untouched dependency setbun audit --audit-level=moderatelocally after the bump → exits cleanweb/package.json(1 line) +web/bun.lock(lockfile regen only)