VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

safer-eval: vulnerability history, versions and safety

safer-eval is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 14 releases, from Oct 2019 to Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C4 M1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all safer-eval vulnerabilities

Vulert verdict on safer-eval 1.3.6 i

Updated on 23 Oct 2026

Careful: 1.3.6 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 36/100
  • Security Some issues to review
  • Maintenance Deprecated
  • Popularity Niche
  • Community Inactive

The registry marks the latest release as deprecated, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.3.6 — affected i
  • Vulnerabilities on record 5 over 1 year · 0 in the last year i
  • Latest disclosure 03 Sep 2020 i
  • Highest CVSS 9.9 i
  • With no published fix 2 i
  • Depended on by 144 packages i
  • Stars 20 i
  • OpenSSF scorecard 1/10 i
  • Last release 82 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for safer-eval, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.3.6 06 Dec 2019 C2 MIT No Details →
1.3.5 14 Jul 2019 C2 MIT No Details →
1.3.4 14 Jul 2019 C2 MIT No Details →
1.3.3 15 May 2019 C3 MIT No Details →
1.3.2 09 Mar 2019 C3 MIT No Details →
1.3.1 27 Feb 2019 C4 M1 MIT No Details →
1.3.0 01 Jan 2019 C4 M1 MIT No Details →
1.2.3 24 Jan 2018 C4 M1 MIT No Details →
1.2.2 16 Mar 2017 C4 M1 MIT No Details →
1.2.1 07 Mar 2017 C4 M1 MIT No Details →
1.2.0 05 Mar 2017 C4 M1 MIT No Details →
1.1.0 04 Mar 2017 C4 M1 MIT No Details →
1.0.1 19 Feb 2017 C4 M1 MIT No Details →
1.0.0 18 Feb 2017 C4 M1 MIT No Details →

All 14 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 3
  • 2020 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for safer-eval

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2019-10760: Sandbox Breakout / Arbitrary Code Execution in safer-eval 9.9 critical 1.3.2 17 Oct 2019
CVE-2019-10759: Sandbox Breakout / Arbitrary Code Execution in safer-eval 9.9 critical 1.3.4 21 Oct 2019
CVE-2019-10769: Sandbox Breakout / Arbitrary Code Execution in safer-eval 9.8 critical No fix published 11 Dec 2019
Sandbox Breakout / Arbitrary Code Execution in safer-eval N/A critical No fix published 03 Sep 2020
Sandbox Breakout / Arbitrary Code Execution in safer-eval N/A medium 1.3.2 19 Aug 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 safer-eval

Is safer-eval safe to use?

Vulert records 5 vulnerabilities for safer-eval in npm: 4 critical, 0 high, 1 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is safer-eval's Vulert package health score?

Vulert scores safer-eval 36/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of safer-eval affected?

Yes. 1.3.6, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does safer-eval have?

5 vulnerabilities are recorded for safer-eval in the npm ecosystem: 4 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new safer-eval vulnerabilities disclosed?

0 vulnerabilities were recorded for safer-eval in the last 12 months, and the oldest entry in this database dates to 17 Oct 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of safer-eval are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor safer-eval for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the safer-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.