How severe is GHSA-r3x4-wr4h-pw33?

GHSA-r3x4-wr4h-pw33 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-r3x4-wr4h-pw33?

GHSA-r3x4-wr4h-pw33 affects the following packages: safer-eval (npm). Ecosystems affected: npm.

How do I fix GHSA-r3x4-wr4h-pw33?

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

How do I detect GHSA-r3x4-wr4h-pw33 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for safer-eval. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-r3x4-wr4h-pw33 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-r3x4-wr4h-pw33?

O3 pinpoints whether GHSA-r3x4-wr4h-pw33 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-r3x4-wr4h-pw33 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-r3x4-wr4h-pw33, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

When was GHSA-r3x4-wr4h-pw33 published, and has it been updated?

GHSA-r3x4-wr4h-pw33 was published on October 21, 2019 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

GHSA-r3x4-wr4h-pw33

CRITICAL

GHSA-r3x4-wr4h-pw33 is a critical-severity (CVSS 9.9) remote code execution vulnerability in safer-eval. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-r3x4-wr4h-pw33 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Sandbox Breakout / Arbitrary Code Execution in safer-eval

Also known asCVE-2019-10759

Published

Oct 21, 2019

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Mar 13, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

12Kdownloads / week

Description

Versions of safer-eval prior to 1.3.4 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code. For example, evaluating he string console.constructor.constructor('return process')().env prints process.env to the console.

Recommendation

Upgrade to version 1.3.4 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`safer-eval`	all versions	1.3.4

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

safer-eval before 1.3.4 are vulnerable to Arbitrary Code Execution. A pa…

snyk.ioNVDJul 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for safer-eval. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update safer-eval to 1.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r3x4-wr4h-pw33 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-r3x4-wr4h-pw33 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-r3x4-wr4h-pw33. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `safer-eval` prior to 1.3.4 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code. For example, evaluating he string `console.constructor.constructor('return process')().env` prints `process.env` to the console. ## Recommendation Upgrade to version 1.3.4 or later.

O3 Security · Impact-Aware SCA

Is GHSA-r3x4-wr4h-pw33 in your dependencies?

O3 detects GHSA-r3x4-wr4h-pw33 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works