N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2025-34146

CVE-2025-34146: @nyariv/sandboxjs has Prototype Pollution vulnerability that may lead to RCE

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2025-34146

CVE-2025-34146:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
@nyariv/sandboxjs	npm	< 0.8.24	0.8.24

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The analysis of the provided patches and vulnerability description indicates a prototype pollution vulnerability in @nyariv/sandboxjs. The root cause is the improper handling of property access for __proto__ within the sandbox's executor logic.

The primary vulnerable function is an anonymous function registered to handle property access (LispType.Prop) within the addOps function in src/executor.ts. The patch in commit d9aa71ae4d1804bc57e5803dae3501432bfa1bff introduces a check for b === '__proto__', ensuring that any attempt to access or modify the prototype chain is properly validated against the configured whitelist. Before this patch, there was no explicit check, allowing malicious code to pollute Object.prototype.

The Sandbox.compile function is also identified as a relevant function, although with medium confidence. It is the main entry point for user-supplied code to enter the sandbox. While the flaw is not in the compile function itself, it is the function that a developer would use to execute untrusted code, which in turn would trigger the vulnerability during its execution by the flawed property access handler. Therefore, a runtime profile of an exploit would likely show Sandbox.compile in the call stack leading to the vulnerable code in the executor.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.