Skip to content

🚨 [security] Update vitest 4.0.18 → 4.1.8 (minor)#24

Closed
depfu[bot] wants to merge 1 commit into
mainfrom
depfu/update/npm/vitest-4.1.8
Closed

🚨 [security] Update vitest 4.0.18 → 4.1.8 (minor)#24
depfu[bot] wants to merge 1 commit into
mainfrom
depfu/update/npm/vitest-4.1.8

Conversation

@depfu

@depfu depfu Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ vitest (4.0.18 → 4.1.8) · Repo

Security Advisories 🚨

🚨 When Vitest UI server is listening, arbitrary file can be read and executed

Summary

Arbitrary file can be read on Windows when Vitest UI server is listening, especially when exposed to the network.

Impact

Only users that match either of the following conditions are affected:

  • explicitly exposes the Vitest UI server to the network (using --api.host or api.host config option)
  • running the Vitest UI or Browser Mode on Windows

Details

The API handler for /__vitest_attachment__ uses the deprecated isFileServingAllowed incorrectly.

    <tbody>
if (!isFileServingAllowed(ctx.vite.config, fsPath)) {

The function expects the passed value to use cleanUrl after the check before file system related operation.
Because of this, it is possible to bypass the check by \\?\\..\\. This is not possible on Linux as Linux errors if a directory named ? does not exist.

A similar problem exists in other places as well.

  •     <tbody>

        <tr class="border-0">
      <td id="L104" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="104"></td>
      <td id="LC104" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line">   <span class="pl-k">return</span> <span class="pl-c1">undefined</span> </td>
    </tr>

    <tr class="border-0">
      <td id="L105" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="105"></td>
      <td id="LC105" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line"> <span class="pl-kos">}</span> </td>
    </tr>
</tbody>
    if (!isFileServingAllowed(testModule.project.vite.config, moduleId)) { 
  •     <tbody>

        <tr class="border-0">
      <td id="L120" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="120"></td>
      <td id="LC120" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line">   <span class="pl-k">return</span> </td>
    </tr>

    <tr class="border-0">
      <td id="L121" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="121"></td>
      <td id="LC121" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line"> <span class="pl-kos">}</span> </td>
    </tr>
</tbody>
    if (!testModule || !isFileServingAllowed(project.vite.config, moduleId)) { 
  •     <tbody>

        <tr class="border-0">
      <td id="L11" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="11"></td>
      <td id="LC11" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line"> <span class="pl-c1">&amp;&amp;</span> <span class="pl-c1">!</span><span class="pl-en">isFileServingAllowed</span><span class="pl-kos">(</span><span class="pl-s1">path</span><span class="pl-kos">,</span> <span class="pl-s1">project</span><span class="pl-kos">.</span><span class="pl-c1">vitest</span><span class="pl-kos">.</span><span class="pl-c1">vite</span><span class="pl-kos">)</span> </td>
    </tr>
</tbody>
    !isFileServingAllowed(path, project.vite) 
  •     <tbody>

        <tr class="border-0">
      <td id="L195" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="195"></td>
      <td id="LC195" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line">   <span class="pl-k">return</span> <span class="pl-en">next</span><span class="pl-kos">(</span><span class="pl-kos">)</span> </td>
    </tr>

    <tr class="border-0">
      <td id="L196" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="196"></td>
      <td id="LC196" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line"> <span class="pl-kos">}</span> </td>
    </tr>
</tbody>
    if (!isFileServingAllowed(parentServer.vite.config, fsPath)) { 
  •     <tbody>

        <tr class="border-0">
      <td id="L116" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="116"></td>
      <td id="LC116" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line">   <span class="pl-k">if</span> <span class="pl-kos">(</span><span class="pl-c1">!</span><span class="pl-en">isFileServingAllowed</span><span class="pl-kos">(</span><span class="pl-s1">path</span><span class="pl-kos">,</span> <span class="pl-s1">vite</span><span class="pl-kos">)</span><span class="pl-kos">)</span> <span class="pl-kos">{</span> </td>
    </tr>

    <tr class="border-0">
      <td id="L117" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="117"></td>
      <td id="LC117" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line">     <span class="pl-k">throw</span> <span class="pl-k">new</span> <span class="pl-v">Error</span><span class="pl-kos">(</span> </td>
    </tr>

    <tr class="border-0">
      <td id="L118" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="118"></td>
      <td id="LC118" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line">       <span class="pl-s">`Access denied to "<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">path</span><span class="pl-kos">}</span></span>". See Vite config documentation for "server.fs": https://vitejs.dev/config/server-options.html#server-fs-strict.`</span><span class="pl-kos">,</span> </td>
    </tr>

    <tr class="border-0">
      <td id="L119" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="119"></td>
      <td id="LC119" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line">     <span class="pl-kos">)</span> </td>
    </tr>

    <tr class="border-0">
      <td id="L120" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="120"></td>
      <td id="LC120" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line">   <span class="pl-kos">}</span> </td>
    </tr>

    <tr class="border-0">
      <td id="L121" class="blob-num border-0 tmp-px-3 py-0 color-bg-default" data-line-number="121"></td>
      <td id="LC121" class="blob-code border-0 tmp-px-3 py-0 color-bg-default blob-code-inner js-file-line"> <span class="pl-kos">}</span> </td>
    </tr>
</tbody>
    function checkFileAccess(path: string) {

That said, this isFileServingAllowed check does not actually prevent the API to be abused. Since the API has rerun feature and file write feature, it's possible to run arbitrary script by writing a script as a test file using saveTestFile and running it using rerun. This means exposing the API / Vitest UI is equivalent to giving script execution access.
On the browser mode side, there're readFile / writeFile / saveSnapshotFile. So exposing the browser mode is equivalent to giving file read / write access.

PoC

  1. Run Vitest UI
  2. Get the API token by curl http://localhost:51204/__vitest__/
  3. Run curl "http://localhost:51204/__vitest_attachment__?path=C:\\path\\to\\project\\?\\..\\..\\secret.txt&amp;contentType=text/plain&amp;token=$TOKEN" (TOKEN is the API token)
  4. curl shows the content of secret.txt that is outside the project directory

Mitigations

Vitest now ships two configuration flags, allowWrite and allowExec, that gate the privileged operations exploited by this vulnerability. Both are disabled by default whenever the API server is bound to a non-localhost host, ensuring that exposing the server to the network no longer implicitly grants write or execute capabilities to remote clients.

When these flags are disabled, the UI also enters a read-only mode: in-browser code editing and test file execution are turned off, removing the attack surface that allowed remote code execution. Many Browser Mode features are also disabled, like attachments, artifacts or snapshots. See browser.api.

Users who require the full interactive UI on a networked host must explicitly opt in by setting allowWrite and/or allowExec to true.

Release Notes

4.1.7

More info than we can show here.

4.1.6

More info than we can show here.

4.1.5

More info than we can show here.

4.1.4

More info than we can show here.

4.1.3

More info than we can show here.

4.1.2

More info than we can show here.

4.1.1

More info than we can show here.

4.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

✳️ @​vitest/coverage-v8 (4.0.18 → 4.1.8) · Repo

Release Notes

4.1.7

More info than we can show here.

4.1.6

More info than we can show here.

4.1.5

More info than we can show here.

4.1.4

More info than we can show here.

4.1.3

More info than we can show here.

4.1.2

More info than we can show here.

4.1.1

More info than we can show here.

4.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​vitest/expect (indirect, 4.0.18 → 4.1.8) · Repo

Release Notes

4.1.7

More info than we can show here.

4.1.6

More info than we can show here.

4.1.5

More info than we can show here.

4.1.4

More info than we can show here.

4.1.3

More info than we can show here.

4.1.2

More info than we can show here.

4.1.1

More info than we can show here.

4.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​vitest/mocker (indirect, 4.0.18 → 4.1.8) · Repo

Release Notes

4.1.7

More info than we can show here.

4.1.6

More info than we can show here.

4.1.5

More info than we can show here.

4.1.4

More info than we can show here.

4.1.3

More info than we can show here.

4.1.2

More info than we can show here.

4.1.1

More info than we can show here.

4.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​vitest/pretty-format (indirect, 4.0.18 → 4.1.8) · Repo

Release Notes

4.1.7

More info than we can show here.

4.1.6

More info than we can show here.

4.1.5

More info than we can show here.

4.1.4

More info than we can show here.

4.1.3

More info than we can show here.

4.1.2

More info than we can show here.

4.1.1

More info than we can show here.

4.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​vitest/runner (indirect, 4.0.18 → 4.1.8) · Repo

Release Notes

4.1.7

More info than we can show here.

4.1.6

More info than we can show here.

4.1.5

More info than we can show here.

4.1.4

More info than we can show here.

4.1.3

More info than we can show here.

4.1.2

More info than we can show here.

4.1.1

More info than we can show here.

4.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​vitest/snapshot (indirect, 4.0.18 → 4.1.8) · Repo

Release Notes

4.1.7

More info than we can show here.

4.1.6

More info than we can show here.

4.1.5

More info than we can show here.

4.1.4

More info than we can show here.

4.1.3

More info than we can show here.

4.1.2

More info than we can show here.

4.1.1

More info than we can show here.

4.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​vitest/spy (indirect, 4.0.18 → 4.1.8) · Repo

Release Notes

4.1.7

More info than we can show here.

4.1.6

More info than we can show here.

4.1.5

More info than we can show here.

4.1.4

More info than we can show here.

4.1.3

More info than we can show here.

4.1.2

More info than we can show here.

4.1.1

More info than we can show here.

4.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​vitest/utils (indirect, 4.0.18 → 4.1.8) · Repo

Release Notes

4.1.7

More info than we can show here.

4.1.6

More info than we can show here.

4.1.5

More info than we can show here.

4.1.4

More info than we can show here.

4.1.3

More info than we can show here.

4.1.2

More info than we can show here.

4.1.1

More info than we can show here.

4.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ ast-v8-to-istanbul (indirect, 0.3.12 → 1.0.3) · Repo

Release Notes

1.0.3

More info than we can show here.

1.0.2

More info than we can show here.

1.0.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ es-module-lexer (indirect, 1.7.0 → 2.1.0) · Repo · Changelog

Release Notes

2.1.0

More info than we can show here.

2.0.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ std-env (indirect, 3.10.0 → 4.1.0) · Repo · Changelog

Release Notes

4.1.0

More info than we can show here.

4.0.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ tinyrainbow (indirect, 3.0.3 → 3.1.0) · Repo

Release Notes

3.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu Bot added the depfu label Jun 1, 2026
@vercel

vercel Bot commented Jun 1, 2026 •
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
flugo-employees Ready Ready Preview, Comment Jun 1, 2026 4:06pm

@guardrails

guardrails Bot commented Jun 1, 2026

Copy link
Copy Markdown

⚠️ We detected 2 security issues in this pull request:

Vulnerable Libraries (2)
Severity Details
Critical pkg:npm/eslint@9.39.4 (t) upgrade to: > 9.39.4
High pkg:npm/vitest@4.1.8 upgrade to: > 4.1.8

More info on how to fix Vulnerable Libraries in JavaScript.

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

@depfu depfu Bot mentioned this pull request Jun 1, 2026
Closed
@depfu

depfu Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor Author

Closed in favor of #28.

@depfu depfu Bot closed this Jun 16, 2026
@depfu depfu Bot deleted the depfu/update/npm/vitest-4.1.8 branch June 16, 2026 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants