happy-dom
21.0.4 · 20 Oct 2026MIT37.6M / weekRepositorynpmAtom feed
20.14.6 is the newest release of 20.x.
In short
2 breaking
- Breaking
When I have to make a breaking change, I try to keep it as minimal as possible.
- Breaking
Due to security risks, JavaScript evaluation is now disabled by default - By @capricorn86 in task #1930
Security
Fixes 1 advisory that affected 19.0.2
- CriticalHappy DOM: VM Context Escape can lead to Remote Code ExecutionGHSA-37j7-fg3j-429f · 10 Oct 2025Fixed in 20.0.0
6 advisories affect 20.0.0; 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
I avoid making breaking changes as much as possible in Happy DOM. When I have to make a breaking change, I try to keep it as minimal as possible. This could be a breaking change that impacts many projects, and I am truly sorry if you are negatively affected by this.
:bomb: Breaking Changes
- Breaking
Due to security risks, JavaScript evaluation is now disabled by default - By @capricorn86 in task #1930
A security advisory (GHSA-37j7-fg3j-429f) has been reported that shows a security vulnerability where it's possible to escape the VM context and get access to process level functionality. Big thanks to @Mas0nShi for reporting this!
Due to this security risk, JavaScript evaluation is now disabled by default to prevent that consumers accidentally executes untrusted code without taking precautions
JavaScript evaluation can be enabled by setting enableJavaScriptEvaluation to "true". Read more about how to enable this in a safer way 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.