Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2025-54782: RCE in @nestjs/devtools-integration

Published Aug 1, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.4Critical · v4
EPSS47.2%99th percentile
CISA KEVNoNot listed
In the wildReported262 exploitation records in Mallory
Vendor
Nestjs
IdentifiersCVE-2025-54782CWE-94

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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.

Mitigation

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.

Remediation

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NestjsDevtools-Integrationapplication
FAQ

Frequently asked questions

Is CVE-2025-54782 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2025-54782?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2025-54782.
Is there a patch for CVE-2025-54782?
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.
What products are affected by CVE-2025-54782?
Nestjs Devtools-Integration.
How severe is CVE-2025-54782?
CVE-2025-54782 has a CVSS v4 score of 9.4 (Critical) and an EPSS score of 47.2% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity18Community discussion across Reddit, Mastodon, and other social sources.