Capricorn86 happy-dom
Happy DOM: Incomplete fix for CVE-2026-33943: unsanitized import alias leads to host code execution
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 17.0.0, < 21.0.4
Fixed in 21.0.4
Mitigation
Upgrade happy-dom to 21.0.4 or later.
References
- Vendor advisory github.com/capricorn86/happy-dom/security/advi…
- Patch github.com/capricorn86/happy-dom/pull/2537
- Patch github.com/capricorn86/happy-dom/commit/fd1635…
1 more
- Release notes github.com/capricorn86/happy-dom/releases/tag/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.