Loading vulnerability…
CVE-2025-24963 affects Vitest browser mode. The browser mode HTTP server includes a __screenshot-error handler that can be abused to return arbitrary files from the host filesystem. According to the provided content, this behavior was introduced by commit 2d62051. When the browser mode server is exposed beyond localhost, particularly with browser.api.host: true, a remote attacker can send crafted requests to the __screenshot-error endpoint and retrieve file contents from the underlying system. The issue is an arbitrary file disclosure vulnerability in the HTTP handler implementation rather than code execution.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
browser.api.host: true unless strictly necessary, bind the service to localhost or trusted interfaces only, and apply network-layer access controls such as firewall rules, reverse-proxy restrictions, or segmentation to prevent remote access until patched.Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository demonstrates a proof-of-concept exploit for CVE-2025-24963, a local file read vulnerability in the @vitest/browser package (versions 2.0.4-2.1.8 and 3.0.0-3.0.3). The vulnerability is triggered when the Vitest browser mode server is configured with 'browser.api.host: true', exposing an HTTP API endpoint (/__screenshot-error) to the network. An attacker can exploit this by sending a crafted HTTP request with a 'file' parameter containing a path traversal payload, allowing arbitrary file reads from the server's filesystem (e.g., /etc/passwd). The repository includes a Dockerfile to set up a vulnerable environment, a minimal test case, and a configuration file that explicitly enables the vulnerable setting. The README provides clear instructions for building, running, and exploiting the demo. The main exploit capability is remote, unauthenticated file read via a network-accessible HTTP endpoint. No weaponized or automated exploit code is present; exploitation is performed via a simple curl command.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.