happy-dom
21.0.4 · 20 Oct 2026MIT37.6M / weekRepositorynpmAtom feed
20.14.6 is the newest release of 20.x.
In short
1 new
Security
6 advisories affect 20.0.1; 21.0.4 fixes the others
- Criticalhappy-dom's `--disallow-code-generation-from-strings` is not sufficient for isolating untrusted JavaScriptGHSA-qpm2-6cq5-7pq5 · 15 Oct 2025Fixed in 20.0.2
- HighHappy DOM: SSRF via iframe and link stylesheet when parsing untrusted HTMLGHSA-c8p4-j97h-3vg8 · 28 Oct 2026No fix yet
- HighHappy DOM: Incomplete fix for CVE-2026-33943: unsanitized import alias leads to host code executionGHSA-834v-8h66-3h79 · 23 Oct 2026Fixed in 21.0.4
- HighHappy DOM's fetch credentials include uses page-origin cookies instead of target-origin cookiesGHSA-w4gp-fjgq-3q4g · 29 Mar 2026Fixed in 20.8.9
- HighHappy DOM ECMAScriptModuleCompiler: unsanitized export names are interpolated as executable codeGHSA-6q6h-j7hj-3r64 · 26 Mar 2026Fixed in 20.8.8
1 more
- ModerateHappy DOM has cookie scope forgery: no DNS-label boundary on Domain= matching , attacker origin sets victim cookiesGHSA-5fpq-26gf-qwcr · 28 Oct 2026Fixed in 20.14.6
Release note
:construction_worker_man: Patch fixes
Adds warning for environment with unfrozen intrinsics (builtins) when JavaScript evaluation is enabled- By @capricorn86 in task #1932
A security advisory has been reported showing that the recommended preventive measure of running Node.js with
--disallow-code-generation-from-stringswasn't enough to protect against attackers escaping the VM context and accessing process-level functions. Big thanks to @cristianstaicu for reporting this!The documentation for how to run Happy DOM with JavaScript evaluation enabled in a safer way has been updated. Read more about it in the Wiki
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.