<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-05T04:07:45.711883+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-115895</id>
    <title>fkie_cve-2026-115895</title>
    <updated>2026-11-05T04:07:45.713411+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-115895"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-834v-8h66-3h79</id>
    <title>GHSA-834v-8h66-3h79 — Happy DOM: Incomplete fix for CVE-2026-33943: unsanitized import alias leads to host code execution</title>
    <updated>2026-11-05T04:07:45.713487+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: happy-dom</p>
<p>## Summary</p>
<p>The ESM compiler in `happy-dom@20.14.5` does not validate imported local binding aliases before interpolating them into generated JavaScript.</p>
<p>As a result, an invalid ESM import alias can be transformed into a valid JavaScript destructuring default initializer and executed.</p>
<p>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.</p>
<p>These issues were confirmed through the public `Window` and `&lt;script type="module"&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.</p>
<p>## Confirmed affected versions</p>
<p>The PoC was directly tested against:</p>
<p>- `happy-dom@17.0.0`
- `happy-dom@20.0.0`
- `happy-dom@20.1.0`
- `happy-dom@20.14.5`</p>
<p>The same PoC does not trigger on `happy-dom@16.8.1`.</p>
<p>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.</p>
<p>Suggested affected range:</p>
<p>```text
&gt;= 17.0.0, &lt;= 20.14.5
```</p>
<p>No patched version is currently available.</p>
<p>## Preconditions</p>
<p>- JavaScript evaluation is enabled with `enableJavaScriptEvaluation: true`.
- Attacker-controlled HTML or module source is processed by Happy D…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-834v-8h66-3h79"/>
  </entry>
</feed>
