Vulnerability Database · npm · safer-eval · Version

safer-eval 1.3.3

1.3.3 is affected by 3 vulnerabilities.

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

Critical 3 High 0 Medium 0 Low 0 Unrated 0

Released 15 May 2019 Status deprecated release Licence MIT Also known from other sources 3 Newer releases 14 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

safer-eval 1.3.3 vulnerabilities

3 vulnerabilities cover safer-eval 1.3.3. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
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

Looking for another version, or everything Vulert holds for safer-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 safer-eval 1.3.3

Is safer-eval 1.3.3 vulnerable?

Yes. 3 vulnerabilities in the Vulert database cover safer-eval 1.3.3: 3 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.

Is 1.3.3 the latest release of safer-eval?

No. 1.3.3 was published 15 May 2019, 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 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.