Loading story…
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.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-53633 was published as a critical remote code execution vulnerability affecting Vitest Browser Mode. The issue exposed a cdp() API that could proxy raw Chrome DevTools Protocol methods and overwrite configuration files to execute attacker-controlled Node.js code; fixes were noted as available in versions 3.2.5, 4.1.8, and 5.0.0-beta.4.
Vitest released version 3.2.5 with new allowWrite and allowExec options and a browser fix that disables the client CDP API when those settings are false. This release backported the change to the v3 branch and represents an available fix for affected versions.
Vitest merged pull request #10445 into the v3 branch, backporting allowWrite and allowExec controls plus a browser change that disables client CDP API access when those settings are false. The PR also included related file access checks, documentation, type updates, and tests for the new defaults.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
5 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.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.
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
Google has patched **CVE-2026-11645**, an actively exploited flaw in Chrome’s V8 JavaScript and WebAssembly engine that can give attackers both out-of-bounds read and write capabilities from a crafted web page. The bug affects Chrome prior to **149.0.7827.103** on Windows and macOS and **149.0.7827.102** on Linux, creating a realistic drive-by compromise path in which renderer-process code execution could be chained with a sandbox escape for full device takeover. Public reporting notes that Google confirmed in-the-wild exploitation but did not disclose the campaign, attribution, or full exploit chain. The risk is amplified across the broader Chromium ecosystem because many **Electron** and Chromium-based applications ship their own embedded V8 runtimes and may remain vulnerable after browser updates. Historical Chromium issues and research around **XSS Auditor** and Chrome security bugs—including bypasses, cross-origin data extraction, form-data leakage through redirects, and Egor Homakov’s account of abusing Chrome bugs in an OAuth flow—underscore how browser flaws can expose sensitive data or be combined into larger attack chains. Organizations are being pushed to update Chrome immediately and inventory Chromium-derived applications that may require separate patch cycles.
Aug 16, 2026
Google Chrome addressed three **use-after-free** vulnerabilities tracked as `CVE-2026-7347`, `CVE-2026-7363`, and `CVE-2026-7344` in versions prior to `147.0.7727.138`. The bugs affect the **Chromoting**, **Canvas**, and **Accessibility** components, respectively, and all were classified under `CWE-416`. Two of the flaws were rated **critical**: `CVE-2026-7363` allows a remote attacker to execute arbitrary code inside the browser sandbox on Linux and ChromeOS by luring a user to a crafted HTML page, while `CVE-2026-7344` could let an attacker escape Chrome's sandbox on Windows after compromising the renderer process via crafted web content. The third issue, `CVE-2026-7347`, was rated **high severity** and affects Chromoting, where malicious network traffic could enable arbitrary code execution without privileges or user interaction. CVSS data added to the records shows network-based exploitation with high impact to confidentiality, integrity, and availability, with `CVE-2026-7363` and `CVE-2026-7344` carrying the vector `AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`. The vulnerabilities were documented in Chrome and Chromium tracking references, underscoring the need for organizations to move affected browsers to `147.0.7727.138` or later.
Jun 29, 2026