Vulnerability · Published Aug 1, 2025 · Assigned by GitHub_M

CVE-2025-54782@nestjs/devtools-integration's CSRF to Sandbox Escape Allows for RCE against JS Developers

Critical 9.4

In plain English

A critical-severity command injection in nest from nestjs. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 47.2% (higher than 99% of all known vulnerabilities). Ready-made attack tooling exists: Nuclei, public proof-of-concept code. Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)9.4Critical
Exploit odds (30 days)47.2%top 1.2% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack tooling2Nuclei, Public PoC

Official description

Nest is a framework for building scalable Node.js server-side applications. In versions 0.2.0 and below, a critical Remote Code Execution (RCE) vulnerability was discovered in the @nestjs/devtools-integration package. When enabled, the package exposes a local development HTTP server with an API endpoint that uses an unsafe JavaScript sandbox (safe-eval-like implementation). Due to improper sandboxing and missing cross-origin protections, any malicious website visited by a developer can execute arbitrary code on their local machine. The package adds HTTP endpoints to a locally running NestJS development server. One of these endpoints, /inspector/graph/interact, accepts JSON input containing a code field and executes the provided code in a Node.js vm.runInNewContext sandbox. This is fixed in version 0.2.1.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npm@nestjs/devtools-integration0.2.1GHSA-85cg-cmq5-qjm7

Affected products (as reported)

VendorProductVersions
nestjs nest < 0.2.1

Weakness: CWE-77, CWE-78, CWE-352 · Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

References