Vulnerability Database · npm · safe-eval · Version

safe-eval 0.3.0

0.3.0 is affected by 6 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 5 High 1 Medium 0 Low 0 Unrated 0

Released 23 May 2016 Licence MIT Also known from other sources 6 Newer releases 6 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

safe-eval 0.3.0 vulnerabilities

6 vulnerabilities cover safe-eval 0.3.0. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2023-26121: Prototype Pollution in safe-eval 10.0 critical No fix published 11 Apr 2023
CVE-2023-26122: Vulnerability in safe-eval package allows Sandbox Bypass 10.0 critical No fix published 11 Apr 2023
CVE-2017-16088: Sandbox Breakout in safe-eval 10.0 critical No fix published 18 Jul 2018
CVE-2022-25904: Prototype Pollution in safe-eval 9.8 critical No fix published 20 Dec 2022
CVE-2020-7710: Sandbox Breakout / Arbitrary Code Execution in safe-eval 9.8 critical No fix published 25 Aug 2020
Sandbox Breakout / Arbitrary Code Execution in safe-eval N/A high No fix published 03 Sep 2020

Looking for another version, or everything Vulert holds for safe-eval?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About safe-eval 0.3.0

Is safe-eval 0.3.0 vulnerable?

Yes. 6 vulnerabilities in the Vulert database cover safe-eval 0.3.0: 5 critical, 1 high, 0 medium and 0 low. Each entry above names the fixed version to move to.

Is 0.3.0 the latest release of safe-eval?

No. 0.3.0 was published 23 May 2016, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor safe-eval for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the safe-eval version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.