CVE-2025-62410None▾ SunlitIn versions before 20.0.2, it was found that --disallow-code-generation-from-strings is not sufficient for isolating untrusted JavaScript in happy-dom. The untrusted script and the rest of the application still run in the same Isolate/pr…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
Last analysed / modified upstream
0.4%
In versions before 20.0.2, it was found that --disallow-code-generation-from-strings is not sufficient for isolating untrusted JavaScript in happy-dom. The untrusted script and the rest of the application still run in the same Isolate/process, so attackers can deploy prototype pollution payloads to hijack important references like "process" in the example below, or to hijack control flow via flipping checks of undefined property. This vulnerability is due to an incomplete fix for CVE-2025-61927. The vulnerability is fixed in 20.0.2.
Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2025-62517Medium· 5.9Rollbar.js offers error tracking and logging from Javascript to Rollbar
CVE-2025-62381Nonesveltekit-superforms makes SvelteKit forms a pleasure to use
CVE-2025-62374Medium· 6.4Parse Javascript SDK provides access to the powerful Parse Server backend from your JavaScript app
CVE-2025-13204High· 7.3npm package `expr-eval` is vulnerable to Prototype Pollution
CVE-2025-64718Medium· 5.3js-yaml is a JavaScript YAML parser and dumper
CVE-2026-107353Medium· 6.5traverse (npm) versions 0.3.6 through 0.3.9, 0.4.0 through 0.4.6, 0.5.0 through 0.5.2, and 0.6.0 through 0.6.11 allow prototype pollution through set()