<?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 13:36:07 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-22223</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-22223</link>
      <description>EUVD-2026-22223</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-22223</guid>
    </item>
    <item>
      <title>fkie_cve-2021-21413</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-21413</link>
      <description>&lt;p&gt;isolated-vm is a library for nodejs which gives you access to v8&amp;#39;s Isolate interface. Versions of isolated-vm before v4.0.0 have API pitfalls which may make it easy for implementers to expose supposed secure isolates to the permissions of the main nodejs isolate. Reference objects allow access to the underlying reference&amp;#39;s full prototype chain. In an environment where the implementer has exposed a Reference instance to an attacker they would be able to use it to acquire a Reference to the nodejs context&amp;#39;s Function object. Similar application-specific attacks could be possible by modifying the local prototype of other API objects. Access to NativeModule objects could allow an attacker to load and run native code from anywhere on the filesystem. If combined with, for example, a file upload API this would allow for arbitrary code execution. This is addressed in v4.0.0 through a series of related changes.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;isolated-vm is a library for nodejs which gives you access to v8&amp;#39;s Isolate interface. Versions of isolated-vm before v4.0.0 have API pitfalls which may make it easy for implementers to expose supposed secure isolates to the permissions of the main nodejs isolate. Reference objects allow access to the underlying reference&amp;#39;s full prototype chain. In an environment where the implementer has exposed a Reference instance to an attacker they would be able to use it to acquire a Reference to the nodejs context&amp;#39;s Function object. Similar application-specific attacks could be possible by modifying the local prototype of other API objects. Access to NativeModule objects could allow an attacker to load and run native code from anywhere on the filesystem. If combined with, for example, a file upload API this would allow for arbitrary code execution. This is addressed in v4.0.0 through a series of related changes.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-21413</guid>
    </item>
    <item>
      <title>GHSA-mmhj-4w6j-76h7 — Misuse of `Reference` and other transferable APIs may lead to access to nodejs isolate</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mmhj-4w6j-76h7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: isolated-vm&lt;/p&gt;
&lt;p&gt;Versions of `isolated-vm` before v4.0.0, and especially before v3.0.0, have API pitfalls which may make it easy for implementers to expose supposed secure isolates to the permissions of the main nodejs isolate.&lt;/p&gt;
&lt;p&gt;`Reference` objects allow access to the underlying reference&amp;#39;s full prototype chain. In an environment where the implementer has exposed a `Reference` instance to an attacker they would be able to use it to acquire a `Reference` to the nodejs context&amp;#39;s `Function` object.&lt;/p&gt;
&lt;p&gt;Similar application-specific attacks could be possible by modifying the local prototype of other API objects.&lt;/p&gt;
&lt;p&gt;Access to `NativeModule` objects could allow an attacker to load and run native code from anywhere on the filesystem. If combined with, for example, a file upload API this would allow for arbitrary code execution.&lt;/p&gt;
&lt;p&gt;To address these issues the following changes were made in v4.0.0:
- Documentation was updated with more explicit guidelines on building secure applications.
- `Reference` instances will no longer follow prototype chains by default, nor will they invoke accessors or proxies.
- All `isolated-vm` API prototypes are now immutable.
- `NativeModule` constructor may only be invoked from a nodejs isolate.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: isolated-vm&lt;/p&gt;
&lt;p&gt;Versions of `isolated-vm` before v4.0.0, and especially before v3.0.0, have API pitfalls which may make it easy for implementers to expose supposed secure isolates to the permissions of the main nodejs isolate.&lt;/p&gt;
&lt;p&gt;`Reference` objects allow access to the underlying reference&amp;#39;s full prototype chain. In an environment where the implementer has exposed a `Reference` instance to an attacker they would be able to use it to acquire a `Reference` to the nodejs context&amp;#39;s `Function` object.&lt;/p&gt;
&lt;p&gt;Similar application-specific attacks could be possible by modifying the local prototype of other API objects.&lt;/p&gt;
&lt;p&gt;Access to `NativeModule` objects could allow an attacker to load and run native code from anywhere on the filesystem. If combined with, for example, a file upload API this would allow for arbitrary code execution.&lt;/p&gt;
&lt;p&gt;To address these issues the following changes were made in v4.0.0:
- Documentation was updated with more explicit guidelines on building secure applications.
- `Reference` instances will no longer follow prototype chains by default, nor will they invoke accessors or proxies.
- All `isolated-vm` API prototypes are now immutable.
- `NativeModule` constructor may only be invoked from a nodejs isolate.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mmhj-4w6j-76h7</guid>
    </item>
    <item>
      <title>gsd-2021-21413</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-21413</link>
      <description>gsd-2021-21413</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-21413</guid>
    </item>
  </channel>
</rss>
