RCE in @nestjs/devtools-integration
CVE-2025-54782 is a critical remote code execution vulnerability in the @nestjs/devtools-integration package for NestJS affecting versions 0.2.0 and below. When the package is enabled, it exposes a local development HTTP server endpoint, including /inspector/graph/interact, that accepts JSON input with a code field. The supplied code is executed using Node.js vm.runInNewContext in an unsafe safe-eval-like sandbox. Because the sandboxing is improper and the exposed endpoint lacks adequate cross-origin protections, a malicious website visited by a developer can send requests to the local development server and cause arbitrary JavaScript to be executed on the developer's machine.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows arbitrary code execution on the local machine of a developer running a vulnerable NestJS development environment with @nestjs/devtools-integration enabled. This can result in full compromise of the developer workstation in the context of the running Node.js process, including theft of source code, credentials, tokens, environment secrets, modification of local files, installation of persistence, and potential pivoting into internal development or CI/CD environments.
If you can’t patch tonight, do this now.
If immediate upgrade is not possible, disable or remove @nestjs/devtools-integration in development environments, especially where the local dev server is running while browsing untrusted websites. Restrict access to the local development HTTP server, avoid exposing the devtools endpoints, and reduce the risk of browser-based cross-origin interaction with localhost services until the package can be updated.
Patch, then assume compromise.
Upgrade @nestjs/devtools-integration to version 0.2.1 or later, which contains the fix for this issue. Ensure all development environments and dependency lockfiles are updated so that vulnerable versions 0.2.0 and below are no longer installed.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.