Loading story…
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:
--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.
Map this exposure pattern across your cloud, code, and identities.
3 events from the most recent confirmed update back to the earliest known activity.
The Nuxt issue was patched in pull request `#35201`, which added an `isLocalDevRequest` check using headers such as `Host`, `Sec-Fetch-Site`, `Origin`, and `Referer`, returning `403 Forbidden` for disallowed requests.
A CVE report described a Nuxt development server issue in which the route `/.well-known/appspecific/com.chrome.devtools.json` exposed workspace metadata, including project configuration and the absolute root directory, without authorization checks.
A GitHub security advisory described a Vitest Browser Mode vulnerability where the cdp() API could proxy raw Chrome DevTools Protocol commands, enabling config overwrite and remote code execution when the API server is exposed to the network.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See where this exposure pattern shows up across your cloud, code, supply chain, and non-human identities.
2 references tracked. Mallory keeps watching after this page renders.
cvereports.com
Open sourcegithub.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.
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
A critical remote code execution flaw tracked as **`CVE-2026-71319`** was disclosed in **Nuxt DevTools** versions prior to **3.3.1**, where the `nuxt:devtools:rpc` plugin exposed an unauthenticated bidirectional RPC channel over the Vite HMR WebSocket in development mode. Because the channel lacked a token requirement, handshake, and origin validation, any reachable client could invoke RPC methods remotely. Attackers could abuse `updateOptions()` to set `behavior.openInEditor` to an arbitrary command and then trigger `openInEditor()` to execute that command on the developer’s machine, making the issue remotely exploitable with a reported **CVSS 9.6** severity. Nuxt addressed the issue in **DevTools 3.3.1** by adding developer-auth token enforcement to previously unauthenticated mutating RPC actions, including operations that persist settings, clear options, and open files in an editor. The fix also updated the client UI to obtain authentication before settings changes and added unit tests to ensure invalid tokens are rejected before side effects occur. Organizations using Nuxt DevTools were advised to upgrade to **3.3.1 or later** and ensure the HMR WebSocket is not exposed externally.
Aug 6, 2026
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