Host code execution via shared prototype pollution
Published Oct 15, 2025 · Updated Oct 15, 2025
Prototype pollution in Happy DOM before 20.0.2 allows remote authenticated users to execute code in the host Node.js process. The VM isolation leaves built-in prototypes shared, letting untrusted scripts replace methods that trusted code later invokes and thereby expose process references. Exploitation requires JavaScript evaluation of attacker-controlled content; successful payloads inherit the host process's data, file, network, and command privileges.
Summary
What happened
Prototype pollution in Happy DOM before 20.0.2 allows remote authenticated users to execute code in the host Node.js process. The VM isolation leaves built-in prototypes shared, letting untrusted scripts replace methods that trusted code later invokes and thereby expose process references. Exploitation requires JavaScript evaluation of attacker-controlled content; successful payloads inherit the host process's data, file, network, and command privileges.
The record
- CVE
- CVE-2025-62410
- Published
- Oct 15, 2025
- Updated
- Oct 15, 2025
- Vendor
- capricorn86
- Product
- Happy DOM
- Classifications
- CWE-1321, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 15, 2025CVE publishedPublication date reported by the CVE source.
- Oct 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 20.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream shared-prototype VM escape proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo