Is this vulnerability remotely exploitable?

Yes, it can be remotely exploitable whenever a remote party can supply JavaScript to be executed in SandboxJS—for example, user-defined scripts, plugins, or multi-tenant business logic. The exploit does not require local system access beyond the ability to run code in the sandbox.

What level of access does an attacker need to exploit this?

An attacker needs the ability to execute or influence JavaScript code inside the SandboxJS environment. No direct access to the host runtime or filesystem is required; the attack works entirely within the structure of the sandboxed code.

What is the safest general fix pattern?

The safest pattern is to redesign sandbox enforcement so that it never relies on attacker-controlled object properties or methods for security-critical decisions. Use immutable, trusted references (e.g., `Object.prototype.hasOwnProperty.call`) or internal metadata for whitelist checks, and comprehensively block access to dangerous prototype-linked properties irrespective of sandbox object state.

Severity:

CRITICAL RISK

(10.0)

Prototype Pollution via Sandbox Escape (CWE-74) in SandboxJS Property Access Controls

CVE-2026-25586

Published:

Feb 6, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Prototype Pollution / Injection

CWE:

CWE-74

Impact:

Sandbox Escape and Prototype Pollution Leading to Arbitrary Code Behavior

Severity:

CRITICAL RISK

(10.0)

CVSS Version:

3.1

Vulnerability Type

Category:

Prototype Pollution / Injection

CWE:

CWE-74

Impact:

Sandbox Escape and Prototype Pollution Leading to Arbitrary Code Behavior

Severity:

CRITICAL RISK

(10.0)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Prototype Pollution via Sandbox Escape (CWE-74) in SandboxJS Property Access Controls

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare