happy-dom
21.0.4 · 20 Oct 2026MIT37.6M / weekRepositorynpmAtom feed
Upgrading happy-dom From 20.0.0 to 20.0.1
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 1
- new
- 0
- fixes
Security
6 advisories still affect 20.0.1
- Happy DOM has cookie scope forgery: no DNS-label boundary on Domain= matching , attacker origin sets victim cookiesmoderate · GHSA-5fpq-26gf-qwcr
- Happy DOM ECMAScriptModuleCompiler: unsanitized export names are interpolated as executable codehigh · GHSA-6q6h-j7hj-3r64
- Happy DOM: Incomplete fix for CVE-2026-33943: unsanitized import alias leads to host code executionhigh · GHSA-834v-8h66-3h79
Upgrading to 21.0.4 clears them.
- 20.0.1
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.
Release by release
- Security
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. - New
Adds warning for environment with unfrozen intrinsics (builtins) when JavaScript evaluation is enabled- By @capricorn86 in task #1932
- Security
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.