This page aggregates publicly disclosed CVE and security risk information related to safe-eval_project, with CVSS, EPSS, publication dates, and vulnerability intelligence data to help assess potential risk and remediation priority.
| CVE | 概要 | ソース | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|---|
| CVE-2023-26122 | All versions of the package safe-eval are vulnerable to Sandbox Bypass due to improper input sanitization. The vulnerability is derived from prototype pollution exploitation. Exploiting this vulnerability might result in remote code execution ("RCE"). **Vulnerable functions:** __defineGetter__, stack(), toLocaleString(), propertyIsEnumerable.call(), valueOf(). | [email protected] | 8.8 | 8.08% | 2023-04-11 | 2025-02-07 |
| CVE-2023-26121 | All versions of the package safe-eval are vulnerable to Prototype Pollution via the safeEval function, due to improper sanitization of its parameter content. | [email protected] | 7.5 | 0.35% | 2023-04-11 | 2025-02-10 |
| CVE-2022-25904 | All versions of package safe-eval are vulnerable to Prototype Pollution which allows an attacker to add or modify properties of the Object.prototype.Consolidate when using the function safeEval. This is because the function uses vm variable, leading an attacker to modify properties of the Object.prototype. | [email protected] | 7.5 | 0.29% | 2022-12-20 | 2025-04-16 |
| CVE-2020-7710 | This affects all versions of package safe-eval. It is possible for an attacker to run an arbitrary command on the host machine. | [email protected] | 8.1 | 0.51% | 2020-08-21 | 2024-11-21 |
| CVE-2017-16088 | The safe-eval module describes itself as a safer version of eval. By accessing the object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox. | [email protected] | 10.0 | 2.06% | 2018-06-07 | 2024-11-21 |