Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Sandbox Breakout / Arbitrary Code Execution in safer-evalGHSA-hgch-jjmr-gp7w

CRITICALFix: commenthol/safer-eval@1c29f6a

GHSA-hgch-jjmr-gp7w is a critical-severity (CVSS 9.9) remote code execution vulnerability in safer-eval. A fix is available for safer-eval — see the affected versions and patch details below.

Also known asCVE-2019-10760SNYK-JS-SAFEREVAL-473029
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
0.45%4.72%8.98%13.2%10.8%2.9%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-hgch-jjmr-gp7w by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

safer-evalnpm
9Kdownloads / week

Description

Versions of safer-eval before 1.3.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code.

Recommendation

Upgrade to version 1.3.2.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmsafer-evalall versions1.3.2npm install safer-eval@1.3.2

Affected Products

1 product · 1 configurations
Application
safer-evalsafer-eval_project
< 1.3.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for safer-eval, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update safer-eval to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hgch-jjmr-gp7w is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Versions of `safer-eval` before 1.3.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code. ## Recommendation Upgrade to version 1.3.2.
O3 Security · Impact-Aware SCA

Is GHSA-hgch-jjmr-gp7w in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Sandbox Breakout / Arbitrary Code Execution in safer-eval