Skip to content

[Snyk] Security upgrade vitest from 4.1.2 to 4.1.8 #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
snyk-io wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade vitest from 4.1.2 to 4.1.8 #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/middleware/express/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,6 @@
"tsdown": "catalog:devTools",
"typescript": "catalog:devTools",
"typescript-eslint": "catalog:devTools",
"vitest": "catalog:devTools"
"vitest": "4.1.8"

@kilo-code-bot kilo-code-bot Bot Jun 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Pin has no effect without lockfile update and leaves other workspace packages vulnerable

This change pins vitest to "4.1.8" in one package, but:

  1. pnpm-lock.yaml still resolves vitest to 4.1.2 (catalog section, lines 78-80). pnpm defers to the lockfile, so this pin is a no-op until the lockfile is regenerated. Snyk itself flagged this: "Failed to update the pnpm-lock.yaml, please update manually before merging."

  2. The vulnerability (SNYK-JS-VITEST-17375131) exists across 12+ packages that all resolve vitest via "catalog:devTools" — only this one package is patched. The catalog specifier in pnpm-workspace.yaml (line 34) is already ^4.0.15, which includes 4.1.8. The proper fix is to regenerate the lockfile so the catalog resolves the patched version workspace-wide, rather than pinning one package and leaving the rest on the vulnerable 4.1.2.

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

}
}
Loading