CVE-2025-32395 is an arbitrary file read vulnerability in the Vite development server affecting versions prior to 6.2.6, 6.1.5, 6.0.15, 5.4.18, and 4.5.13. When Vite is run on Node or Bun, malformed HTTP requests containing a '#' character in the request-target may be passed to userland instead of being rejected. Vite assumed req.url would not contain '#', and this assumption caused its server.fs.deny protection to be bypassed. An attacker can leverage this behavior, including with the @fs path handling and a URL-encoded hash character (%23), to cause the dev server to return the contents of arbitrary files to the browser. The issue does not affect Deno in the described scenario.
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.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An arbitrary file read vulnerability in the Vite dev server, referenced by CVE-2025-32395.
An arbitrary file read vulnerability in the Vite dev server that allows attackers to bypass fs.deny protections using the @fs prefix with a URL-encoded hash character (%23).
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.