For your digest
@vitest/mocker, vitest: Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- @vitest/mocker (npm): from 2.1.0, before 4.1.11
- vitest (npm): from 2.1.0, before 4.1.11
- vitest (npm): from 5.0.0-beta.1, before 5.0.0-rc.2
- @vitest/mocker (npm): from 5.0.0-beta.1, before 5.0.0-rc.2
The fix
@vitest/mocker (npm) fixed in 4.1.11
npmnpm install "@vitest/mocker@4.1.11"pnpmpnpm add "@vitest/mocker@4.1.11"yarnyarn add "@vitest/mocker@4.1.11"bunbun add "@vitest/mocker@4.1.11"Check what is installednpm ls @vitest/mockerPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @vitest/mocker to 4.1.11 or the nearest later release, to fix CVE-2026-84373. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@vitest/mocker (npm) fixed in 5.0.0-rc.2
npmnpm install "@vitest/mocker@5.0.0-rc.2"pnpmpnpm add "@vitest/mocker@5.0.0-rc.2"yarnyarn add "@vitest/mocker@5.0.0-rc.2"bunbun add "@vitest/mocker@5.0.0-rc.2"Check what is installednpm ls @vitest/mockerPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @vitest/mocker to 5.0.0-rc.2 or the nearest later release, to fix CVE-2026-84373. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vitest (npm) fixed in 4.1.11
npmnpm install vitest@4.1.11pnpmpnpm add vitest@4.1.11yarnyarn add vitest@4.1.11bunbun add vitest@4.1.11Check what is installednpm ls vitestPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vitest to 4.1.11 or the nearest later release, to fix CVE-2026-84373. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vitest (npm) fixed in 5.0.0-rc.2
npmnpm install vitest@5.0.0-rc.2pnpmpnpm add vitest@5.0.0-rc.2yarnyarn add vitest@5.0.0-rc.2bunbun add vitest@5.0.0-rc.2Check what is installednpm ls vitestPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vitest to 5.0.0-rc.2 or the nearest later release, to fix CVE-2026-84373. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".