cve.bz

CVE-2025-62410 capricorn86 happy-dom: Prototype Pollution

9.4 criticalEPSS 0.4%Fix available

Critical (9.4) in capricorn86 happy-dom. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in happy-dom 20.0.2.

On this page
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.

Severity

CVSS 4.0

9.4 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2025-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1321 Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution)
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • happy-dom (npm): fixed in 20.0.2

Ask an AI about this CVE

Show the promptExplain CVE-2025-62410 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-62410?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-62410?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-62410 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
capricorn86 happy-dom< 20.0.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qpm2-6cq5-7pq5npmhappy-dom>=19.0.0 <20.0.220.0.2

Red Hat

Red Hat rates this Important.

Red Hat's statement

The impact is IMPORTANT because disabling dynamic code generation alone does not create a separate execution context. Trusted and untrusted code still share the same global prototypes and intrinsic objects; a polluted prototype is immediately visible to the rest of the process.

The flaw arises from incomplete sandboxing. The mitigation for dynamic code generation only blocks eval and Function but does not isolate execution contexts. As both trusted and untrusted scripts share prototypes in one isolate, a polluted built-in can redirect internal lookups or override constructors to expose privileged globals. This enables arbitrary command execution from within the supposedly restricted environment.

ProductPackageStateAdvisory
Red Hat OpenShift Dev Spacesdevspaces/traefik-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-62410.

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON