<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 17:37:41 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-13414</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-13414</link>
      <description>bdu:2025-13414</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-13414</guid>
    </item>
    <item>
      <title>EUVD-2026-248954</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-248954</link>
      <description>EUVD-2026-248954</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-248954</guid>
    </item>
    <item>
      <title>fkie_cve-2025-54782</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-54782</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-54782</guid>
    </item>
    <item>
      <title>GHSA-85cg-cmq5-qjm7 — @nestjs/devtools-integration: CSRF to Sandbox Escape Allows for RCE against JS Developers</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-85cg-cmq5-qjm7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nestjs/devtools-integration&lt;/p&gt;
&lt;p&gt;## Summary
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.&lt;/p&gt;
&lt;p&gt;A full blog post about how this vulnerability was uncovered can be found on [Socket&amp;#39;s blog](https://socket.dev/blog/nestjs-rce-vuln).&lt;/p&gt;
&lt;p&gt;## Details
The `@nestjs/devtools-integration` 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.&lt;/p&gt;
&lt;p&gt;Key issues:
1. **Unsafe Sandbox:** The sandbox implementation closely resembles the abandoned `safe-eval` library. The Node.js `vm` module is [explicitly documented](https://nodejs.org/api/vm.html) as not providing a security mechanism for executing untrusted code. Numerous known sandbox escape techniques allow arbitrary code execution.
2. **Lack of Proper CORS/Origin Checking:** The server sets `Access-Control-Allow-Origin` to a fixed domain (`https://devtools.nestjs.com`) but does not validate the request&amp;#39;s `Origin` or `Content-Type`. Attackers can craft POST requests with `text/plain` content type using HTML f…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nestjs/devtools-integration&lt;/p&gt;
&lt;p&gt;## Summary
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.&lt;/p&gt;
&lt;p&gt;A full blog post about how this vulnerability was uncovered can be found on [Socket&amp;#39;s blog](https://socket.dev/blog/nestjs-rce-vuln).&lt;/p&gt;
&lt;p&gt;## Details
The `@nestjs/devtools-integration` 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.&lt;/p&gt;
&lt;p&gt;Key issues:
1. **Unsafe Sandbox:** The sandbox implementation closely resembles the abandoned `safe-eval` library. The Node.js `vm` module is [explicitly documented](https://nodejs.org/api/vm.html) as not providing a security mechanism for executing untrusted code. Numerous known sandbox escape techniques allow arbitrary code execution.
2. **Lack of Proper CORS/Origin Checking:** The server sets `Access-Control-Allow-Origin` to a fixed domain (`https://devtools.nestjs.com`) but does not validate the request&amp;#39;s `Origin` or `Content-Type`. Attackers can craft POST requests with `text/plain` content type using HTML f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-85cg-cmq5-qjm7</guid>
    </item>
  </channel>
</rss>
