<?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://db.gcve.eu</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, 05 Nov 2026 04:07:46 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-115895</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-115895</link>
      <description>&lt;p&gt;Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. From 17.0.0 until 21.0.4, packages/happy-dom/src/module/ECMAScriptModuleCompiler.ts accepts a named ESM import alias without validating that it is a JavaScript binding identifier before inserting it into a generated destructuring binding. With enableJavaScriptEvaluation enabled, attacker-controlled HTML or module source can use an invalid alias that becomes a valid default initializer after compilation, causing the generated JavaScript to execute in the Node.js host process. The demonstrated reachable path uses a JSON module import attribute, which prevents the malicious alias from being emitted again in a later ESM circular-import assignment and keeps the generated function syntactically valid. This incomplete fix for CVE-2026-33943 is a distinct residual path because the earlier remediation validated the local export importName path but not the named-import alias. This issue is fixed in version 21.0.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. From 17.0.0 until 21.0.4, packages/happy-dom/src/module/ECMAScriptModuleCompiler.ts accepts a named ESM import alias without validating that it is a JavaScript binding identifier before inserting it into a generated destructuring binding. With enableJavaScriptEvaluation enabled, attacker-controlled HTML or module source can use an invalid alias that becomes a valid default initializer after compilation, causing the generated JavaScript to execute in the Node.js host process. The demonstrated reachable path uses a JSON module import attribute, which prevents the malicious alias from being emitted again in a later ESM circular-import assignment and keeps the generated function syntactically valid. This incomplete fix for CVE-2026-33943 is a distinct residual path because the earlier remediation validated the local export importName path but not the named-import alias. This issue is fixed in version 21.0.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-115895</guid>
    </item>
    <item>
      <title>GHSA-834v-8h66-3h79 — Happy DOM: Incomplete fix for CVE-2026-33943: unsanitized import alias leads to host code execution</title>
      <link>https://db.gcve.eu/vuln/ghsa-834v-8h66-3h79</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: happy-dom&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The ESM compiler in `happy-dom@20.14.5` does not validate imported local binding aliases before interpolating them into generated JavaScript.&lt;/p&gt;
&lt;p&gt;As a result, an invalid ESM import alias can be transformed into a valid JavaScript destructuring default initializer and executed.&lt;/p&gt;
&lt;p&gt;This appears to be an alternate injection path and incomplete remediation of GHSA-6q6h-j7hj-3r64 / CVE-2026-33943. The previous fix validates `importName` in the local `export { ... }` handler, but the named import handler still places an unvalidated `alias` directly into code context.&lt;/p&gt;
&lt;p&gt;These issues were confirmed through the public `Window` and `&amp;lt;script type=&amp;#34;module&amp;#34;&amp;gt;` APIs using the published `happy-dom` npm package. The PoC reaches the Node.js host `process`, obtains `node:fs`, and creates a proof directory on the host filesystem.&lt;/p&gt;
&lt;p&gt;## Confirmed affected versions&lt;/p&gt;
&lt;p&gt;The PoC was directly tested against:&lt;/p&gt;
&lt;p&gt;- `happy-dom@17.0.0`
- `happy-dom@20.0.0`
- `happy-dom@20.1.0`
- `happy-dom@20.14.5`&lt;/p&gt;
&lt;p&gt;The same PoC does not trigger on `happy-dom@16.8.1`.&lt;/p&gt;
&lt;p&gt;The ESM compiler was introduced by commit `7bc831df2`, first released in `v17.0.0`. The vulnerable interpolation remains present through `v20.14.5`, the latest release at the time of testing.&lt;/p&gt;
&lt;p&gt;Suggested affected range:&lt;/p&gt;
&lt;p&gt;```text
&amp;gt;= 17.0.0, &amp;lt;= 20.14.5
```&lt;/p&gt;
&lt;p&gt;No patched version is currently available.&lt;/p&gt;
&lt;p&gt;## Preconditions&lt;/p&gt;
&lt;p&gt;- JavaScript evaluation is enabled with `enableJavaScriptEvaluation: true`.
- Attacker-controlled HTML or module source is processed by Happy D…&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&lt;/p&gt;
&lt;p&gt;The ESM compiler in `happy-dom@20.14.5` does not validate imported local binding aliases before interpolating them into generated JavaScript.&lt;/p&gt;
&lt;p&gt;As a result, an invalid ESM import alias can be transformed into a valid JavaScript destructuring default initializer and executed.&lt;/p&gt;
&lt;p&gt;This appears to be an alternate injection path and incomplete remediation of GHSA-6q6h-j7hj-3r64 / CVE-2026-33943. The previous fix validates `importName` in the local `export { ... }` handler, but the named import handler still places an unvalidated `alias` directly into code context.&lt;/p&gt;
&lt;p&gt;These issues were confirmed through the public `Window` and `&amp;lt;script type=&amp;#34;module&amp;#34;&amp;gt;` APIs using the published `happy-dom` npm package. The PoC reaches the Node.js host `process`, obtains `node:fs`, and creates a proof directory on the host filesystem.&lt;/p&gt;
&lt;p&gt;## Confirmed affected versions&lt;/p&gt;
&lt;p&gt;The PoC was directly tested against:&lt;/p&gt;
&lt;p&gt;- `happy-dom@17.0.0`
- `happy-dom@20.0.0`
- `happy-dom@20.1.0`
- `happy-dom@20.14.5`&lt;/p&gt;
&lt;p&gt;The same PoC does not trigger on `happy-dom@16.8.1`.&lt;/p&gt;
&lt;p&gt;The ESM compiler was introduced by commit `7bc831df2`, first released in `v17.0.0`. The vulnerable interpolation remains present through `v20.14.5`, the latest release at the time of testing.&lt;/p&gt;
&lt;p&gt;Suggested affected range:&lt;/p&gt;
&lt;p&gt;```text
&amp;gt;= 17.0.0, &amp;lt;= 20.14.5
```&lt;/p&gt;
&lt;p&gt;No patched version is currently available.&lt;/p&gt;
&lt;p&gt;## Preconditions&lt;/p&gt;
&lt;p&gt;- JavaScript evaluation is enabled with `enableJavaScriptEvaluation: true`.
- Attacker-controlled HTML or module source is processed by Happy D…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-834v-8h66-3h79</guid>
    </item>
  </channel>
</rss>
