CVE-2025-24963

__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.

Details

This __screenshot-error handler on the browser mode HTTP server responds any file on the file system.
https://github.com/vitest-dev/vitest/blob/f17918a79969d27a415f70431e08a9445b051e45/packages/browser/src/node/plugin.ts#L88-L130

This code was added by https://github.com/vitest-dev/vitest/commit/2d62051f13b4b0939b2f7e94e88006d830dc4d1f.

PoC

1. Create a directory and change the current directory to that directory
2. Run npx vitest init browser
3. Run npm run test:browser
4. Run curl http://localhost:63315/__screenshot-error?file=/path/to/any/file

Users explicitly exposing the browser mode server to the network by browser.api.host: true may get any files exposed.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2025-24963 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.1.9, 3.0.4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-24963? CVE-2025-24963 is a medium-severity path traversal vulnerability in @vitest/browser (npm), affecting versions >= 2.0.4, < 2.1.9. It is fixed in 2.1.9, 3.0.4. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2025-24963? CVE-2025-24963 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @vitest/browser are affected by CVE-2025-24963? @vitest/browser (npm) versions >= 2.0.4, < 2.1.9 is affected.
4. Is there a fix for CVE-2025-24963? Yes. CVE-2025-24963 is fixed in 2.1.9, 3.0.4. Upgrade to this version or later.
5. Is CVE-2025-24963 exploitable, and should I be worried? Whether CVE-2025-24963 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-24963 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-24963?
   • Upgrade @vitest/browser to 2.1.9 or later
   • Upgrade @vitest/browser to 3.0.4 or later