Loading story…
A large-scale campaign exploited CVE-2026-39364 to extract sensitive files from internet-exposed Vite development servers. The CVSS 8.2 file-disclosure flaw affects Vite versions 7.1.0–7.3.1 and 8.0.0–8.0.4, allowing unauthenticated requests to bypass server.fs.deny restrictions via crafted @fs paths and query parameters. F5 honeypots logged 807 session-grouped attacks and about 32,000 raw events during August, a substantial increase over preceding Vite-related activity.
Attackers sought .env files, AWS credentials and configuration, Azure profiles, Terraform and Serverless Framework state artifacts, and Linux process and system data. Requests used encoded path traversal, impersonated major crawler and AI-bot user agents, forged forwarding headers, and often originated from Google Cloud address space. Organizations should upgrade to Vite 7.3.2, 8.0.5, or a later supported release; remove development servers from public exposure; investigate logs and cloud audit trails; and rotate any credentials or secrets that may have been disclosed.
See which actors are running it and whether you're in range.
3 events from the most recent confirmed update back to the earliest known activity.
Attackers conducted an automated campaign against internet-exposed Vite development servers, primarily exploiting CVE-2026-39364 to seek .env files, AWS and Azure credentials, Terraform and Serverless artifacts, and process-environment data. F5 honeypots recorded 807 session-grouped attacks and about 32,000 raw Vite-related events; the scanners used encoded paths, spoofed crawler user agents, forged forwarding headers, and largely cloud-hosted source infrastructure.
Vite published an advisory for CVE-2026-39364, a high-severity vulnerability that allows unauthenticated retrieval of files blocked by server.fs.deny through crafted query parameters on the /@fs/ route.
CISA added CVE-2025-31125, a related file-access bypass vulnerability whose signatures were later triggered by Vite scanning traffic, to its Known Exploited Vulnerabilities catalog.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Correlate live exploitation activity against the software you actually run, and see where you're exposed.
4 references tracked. Mallory keeps watching after this page renders.
csoonline.com
Open sourcethehackernews.com
Open sourcecybersecuritynews.com
Open sourcecryptika.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Two vulnerabilities in the Vite development server can let unauthenticated attackers read sensitive local files when the server is reachable over a network. One flaw allows `server.fs.deny` protections to be bypassed by appending Vite-recognized query parameters such as `?raw`, `?import&raw`, or `?url&inline` to requests, enabling disclosure of files like `.env` in HTTP responses. The exposure is especially severe when developers bind Vite to all interfaces, including with `--host 0.0.0.0`, for testing across devices or network segments. A second issue affects Vite’s WebSocket RPC interface, where an attacker can connect directly—or potentially through Cross-Site WebSocket Hijacking if origin checks are weak—and send a crafted `vite:invoke` request calling `fetchModule` with an absolute `file://` path and `?raw`. The server can then return the targeted file’s contents inside a JSON response wrapped as JavaScript exports, allowing attackers to recover local data from the developer system. Together, the flaws show that exposed Vite dev servers can become a path to arbitrary file read and leakage of secrets stored on disk.
Jun 29, 2026
Security disclosures detailed two development-server flaws that exposed sensitive local project information over network-accessible endpoints. In Nuxt, the route `/.well-known/appspecific/com.chrome.devtools.json` returned workspace metadata, including project configuration, a workspace UUID, and the absolute project root directory, without authorization checks. The issue was fixed in pull request `#35201` by adding an `isLocalDevRequest` check that validates headers such as `Host`, `Sec-Fetch-Site`, `Origin`, and `Referer`, returning `403 Forbidden` for disallowed requests; the advisory also noted a limitation affecting some IPv6 localhost requests with ports. A separate advisory warned that Vitest Browser Mode could expose enough browser-runner data to let remote attackers authenticate to the API, proxy raw Chrome DevTools Protocol commands through `cdp()`, overwrite `vite.config.ts`, and execute attacker-controlled Node.js code on the host even when `allowWrite` and `allowExec` were disabled. The attack was possible when the Browser Mode API server was exposed to the network, such as: ```bash --browser.api.host=0.0.0.0 ``` and could also be used to run JavaScript in the browser session and probe local files via `file://` navigation, turning development tooling exposure into a high-impact confidentiality and code-execution risk.
Jun 29, 2026
A critical remote code execution vulnerability, **CVE-2026-53633**, was disclosed in Vitest Browser Mode after researchers found that the exposed `cdp()` API could forward raw Chrome DevTools Protocol requests without properly enforcing `allowWrite` or `allowExec` restrictions. An attacker with access to exposed browser API metadata could abuse methods such as `Page.setDownloadBehavior` and `Runtime.evaluate` to overwrite `vite.config.ts` and run attacker-controlled Node.js code, making the issue remotely exploitable and earning a **CVSS 9.8** rating. The flaw affects Vitest versions `3.0.0` through before `3.2.5`, `4.0.0` through before `4.1.8`, and `5.0.0-beta.0` through before `5.0.0-beta.4`. Maintainers addressed the issue in release `3.2.5` by adding `allowWrite` and `allowExec` options and disabling the client CDP API when those settings are false; corresponding fixes are also available in versions `4.1.8` and `5.0.0-beta.4`. Organizations using Vitest Browser Mode should upgrade to the patched releases and review whether browser-facing API metadata is exposed in reachable environments.
Jul 15, 2026