--disallow-code-generation-from-strings is not sufficient for isolating untrusted JavaScript in happy-dom
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| capricorn86 | happy-dom | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Capricorn86 | Happy-dom | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-qpm2-6cq5-7pq5 | happy-dom's `--disallow-code-generation-from-strings` is not sufficient for isolating untrusted JavaScript |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.360% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Capricorn86
Capricorn86 happy-dom |
|
| Vendors & Products |
Capricorn86
Capricorn86 happy-dom |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | --disallow-code-generation-from-strings is not sufficient for isolating untrusted JavaScript in happy-dom | |
| Weaknesses | CWE-1321 | |
| References |
| |
| Metrics |
cvssV4_0
|