本頁列出影響 safe-eval_project safe-eval 的已公開 CVE 漏洞（透過 NVD CPE 關聯）。每列包含嚴重程度評分、摘要與發布日期，便於識別與分析安全議題。
| 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 | 2.10% | 2023-04-11 | 2026-06-17 |
| 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 | 1.11% | 2023-04-11 | 2026-06-17 |
| 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.88% | 2022-12-20 | 2026-06-17 |
| 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 | 1.43% | 2020-08-21 | 2026-06-16 |
| 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 | 3.49% | 2018-06-06 | 2026-06-16 |