Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

Sandbox Breakout / Arbitrary Code Execution in safer-eval

CVE-2019-10769GHSA-v63x-xc9j-hhvq

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm safer-eval

    Affected
    <= 1.3.6
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2019-10769: 2.60% estimated exploitation activity in the next 30 days; percentile 85.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

All versions of safer-eval are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context and is not suited to process arbitrary user input. This may allow attackers to execute arbitrary code in the system. Recommendation The package is not meant to receive user input. Consider using an alternative package until a fix is made available.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-v63x-xc9j-hhvq

  2. Revision 1 · created ·

    Published from osv record GHSA-v63x-xc9j-hhvq

Agent brief

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

# Patch Next advisory brief: CVE-2019-10769

Advisory: Sandbox Breakout / Arbitrary Code Execution in safer-eval
IDs: CVE-2019-10769, GHSA-v63x-xc9j-hhvq
Record: https://patchnext.com/advisories/cve-2019-10769 (revision 2, source checked 26 Oct 2026, 12:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm safer-eval: affected <= 1.3.6

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on safer-eval.
- 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://osv.dev/vulnerability/GHSA-v63x-xc9j-hhvq (OSV record GHSA-v63x-xc9j-hhvq lists affected ranges: npm safer-eval >=0 <=1.3.6)
- Verified: https://github.com/advisories/GHSA-v63x-xc9j-hhvq (GitHub-reviewed advisory GHSA-v63x-xc9j-hhvq lists affected ranges: npm safer-eval >=0 <=1.3.6)

Commands are suggestions: review each one before running it.

Loading voting…