How severe is GHSA-9qm3-6qrr-c76m?

No CVSS score has been assigned to GHSA-9qm3-6qrr-c76m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9qm3-6qrr-c76m?

GHSA-9qm3-6qrr-c76m affects the following packages: @nyariv/sandboxjs (npm). Ecosystems affected: npm.

How do I fix GHSA-9qm3-6qrr-c76m?

Update @nyariv/sandboxjs to 0.8.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9qm3-6qrr-c76m is resolved across your whole dependency graph.

How do I detect GHSA-9qm3-6qrr-c76m in my npm dependencies?

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

How do I mitigate GHSA-9qm3-6qrr-c76m if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-9qm3-6qrr-c76m actively exploited in the wild?

No public exploit code has been indexed for GHSA-9qm3-6qrr-c76m 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.

What is the EPSS score for GHSA-9qm3-6qrr-c76m?

GHSA-9qm3-6qrr-c76m has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-9qm3-6qrr-c76m?

GHSA-9qm3-6qrr-c76m is classified as CWE-1321 (CWE-1321). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9qm3-6qrr-c76m published, and has it been updated?

GHSA-9qm3-6qrr-c76m was published on July 31, 2025 and was last updated on July 31, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

@nyariv/sandboxjs has Prototype Pollution vulnerability…

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9qm3-6qrr-c76m.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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.

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

@nyariv/sandboxjsnpm

117Kdownloads / week

Description

A prototype pollution vulnerability exists in @nyariv/sandboxjs versions <= 0.8.23, allowing attackers to inject arbitrary properties into Object.prototype via crafted JavaScript code. This can result in a denial-of-service (DoS) condition or, under certain conditions, escape the sandboxed environment intended to restrict code execution. The vulnerability stems from insufficient prototype access checks in the sandbox’s executor logic, particularly in the handling of JavaScript function objects returned.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@nyariv/sandboxjs`	all versions	0.8.24`npm install @nyariv/sandboxjs@0.8.24`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nyariv/sandboxjs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @nyariv/sandboxjs to 0.8.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9qm3-6qrr-c76m is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

A prototype pollution vulnerability exists in @nyariv/sandboxjs versions <= 0.8.23, allowing attackers to inject arbitrary properties into Object.prototype via crafted JavaScript code. This can result in a denial-of-service (DoS) condition or, under certain conditions, escape the sandboxed environment intended to restrict code execution. The vulnerability stems from insufficient prototype access checks in the sandbox’s executor logic, particularly in the handling of JavaScript function objects returned.

O3 Security · Impact-Aware SCA

Is GHSA-9qm3-6qrr-c76m in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

@nyariv/sandboxjs has Prototype Pollution vulnerability that may lead to RCEGHSA-9qm3-6qrr-c76m