SandboxJS Vulnerable to Prototype Pollution -> Sandbox Escape -> RCE

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-25142: 1.21% estimated exploitation activity in the next 30 days; percentile 68.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary SandboxJS does not properly restrict lookupGetter which can be used to obtain prototypes, which can be used for escaping the sandbox / remote code execution. Details https://github.com/nyariv/SandboxJS/blob/f212a38fb5a6d4bc2bc2e2466c0c011ce8d41072/src/executor.ts#L368-L398 The Object prototype which contains lookupGetter is properly protected, but the special case for accessing function properties bypasses the prototype chain checks including the root Object prototype. PoC Impact Prototype Pollution - RCE

Published by the source

2 Feb 2026, 20:17 UTC

Last modified by the source

18 Feb 2026, 23:56 UTC

Source last checked

26 Oct 2026, 12:42 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9p4w-fq8m-2hp7

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-9p4w-fq8m-2hp7

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-9p4w-fq8m-2hp7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25142

Advisory: SandboxJS Vulnerable to Prototype Pollution -> Sandbox Escape -> RCE
IDs: CVE-2026-25142, GHSA-9p4w-fq8m-2hp7
Record: https://patchnext.com/advisories/cve-2026-25142 (revision 3, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @nyariv/sandboxjs 0.8.27. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @nyariv/sandboxjs: affected <= 0.8.26; fixed in 0.8.27

## Suggested inspection (read-only)
- `npm ls @nyariv/sandboxjs --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @nyariv/sandboxjs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9p4w-fq8m-2hp7 (GitHub-reviewed advisory GHSA-9p4w-fq8m-2hp7 lists affected ranges: npm @nyariv/sandboxjs >=0 <=0.8.26)
- Verified: https://osv.dev/vulnerability/GHSA-9p4w-fq8m-2hp7 (OSV record GHSA-9p4w-fq8m-2hp7 lists affected ranges: npm @nyariv/sandboxjs >=0 <0.8.27 (fixed))

Commands are suggestions: review each one before running it.