Skip to content

Commit 8c2692c

Browse files
committed
fix(graph-ui): bump vitest past the @vitest/mocker path traversal
GHSA-82fw-gwwq-j7x9: path traversal / arbitrary file read via the @vitest/mocker redirect mock, CVSS 5.9, affecting >= 2.1.0 < 4.1.11. graph-ui resolved 4.1.8. Development scope, and graph-ui appears nowhere in scripts/package-release.sh, so no released artifact was ever exposed. It is fixed rather than reasoned around because it is the repository's only open code-scanning alert, and the gate that is supposed to act on it cannot do its job while it stands. The manifest floor moves ^4.1.0 -> ^4.1.11 as well as the lockfile, so a fresh npm install cannot resolve back into the vulnerable range. graph-ui: npm ci clean, 47 tests across 12 files pass on 4.1.11. Split from the code-scanning gate fix deliberately. That change makes the gate able to see open alerts and fail closed; merging it while this alert is still open would block it on the very condition it exists to detect. Landing the bump first lets Scorecard rescan main (it runs on push) and clear the alert, after which the gate fix merges against a clean slate. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
1 parent 9da4d66 commit 8c2692c

2 files changed

Lines changed: 49 additions & 49 deletions

File tree

‎graph-ui/package-lock.json‎

Lines changed: 48 additions & 48 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎graph-ui/package.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@
3737
"tailwindcss": "^4.1.0",
3838
"typescript": "^5.7.0",
3939
"vite": "^6.4.3",
40-
"vitest": "^4.1.0"
40+
"vitest": "^4.1.11"
4141
},
4242
"overrides": {
4343
"form-data": ">=4.0.6",

0 commit comments

Comments
 (0)