# CVE-2025-24963: Browser mode serves arbitrary files in vitest

> Attackers can read arbitrary files from the server if the Vitest browser mode is explicitly exposed to the network.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-8gvc-j273-4wm5

## What is CVE-2025-24963?

CVE-2025-24963 is a medium-severity path traversal vulnerability in vitest-dev vitest, published on 4 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vitest is a testing framework powered by Vite. The `__screenshot-error` handler on the browser mode HTTP server that responds any file on the file system. Especially if the server is exposed on the network by `browser.api.host: true`, an attacker can send a request to that handler from remote to get the content of arbitrary files.This `__screenshot-error` handler on the browser mode HTTP server responds any file on the file system. This code was added by commit `2d62051`. Users explicitly exposing the browser mode server to the network by `browser.api.host: true` may get any files exposed. This issue has been addressed in versions 2.1.9 and 3.0.4. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-24963?

4 open source packages ship an affected version, including @vitest/browser. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@vitest/browser` | npm | From 2.0.4 | 2.1.9 |
| `@vitest/browser` | npm | From 2.0.4 | 2.1.9 |
| `@vitest/browser` | npm | From 3.0.0 | 3.0.4 |
| `@vitest/browser` | npm | From 3.0.0 | 3.0.4 |

Products: Vitest.dev Vitest.

## How do I fix CVE-2025-24963?

Upgrade @vitest/browser to a fixed version for your release line: 2.1.9 or 3.0.4.

## Is CVE-2025-24963 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24963 exists.

Public exploit code:

- https://github.com/hiteshpatra/CVE-2025-24963 (github_poc): https://github.com/hiteshpatra/CVE-2025-24963
- Vitest Browser Mode - Local File Read (nuclei): http/cves/2025/CVE-2025-24963.yaml

## Other vulnerabilities in vitest-dev vitest

- [CVE-2026-47429](https://insights.sbomify.com/CVE-2026-47429/): Vitest: Arbitrary file can be read and executed when Vitest UI server is listening (critical 9.8)
- [CVE-2025-24964](https://insights.sbomify.com/CVE-2025-24964/): Remote Code Execution when accessing a malicious website while Vitest API server is listening (critical 9.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24963 and fix it if it is affected.

What it is: CVE-2025-24963 is a medium-severity path traversal vulnerability in vitest-dev vitest, published on 4 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24963 exists.

Affected packages and fixed versions:
- @vitest/browser (npm): affected from 2.0.4; fixed in 2.1.9
- @vitest/browser (npm): affected from 2.0.4; fixed in 2.1.9
- @vitest/browser (npm): affected from 3.0.0; fixed in 3.0.4
- @vitest/browser (npm): affected from 3.0.0; fixed in 3.0.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24963/ (Markdown: https://insights.sbomify.com/CVE-2025-24963/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24963
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24963
- OSV: https://osv.dev/vulnerability/CVE-2025-24963

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24963/
Summaries are generated and may contain mistakes; the official description above is the record.