CVE-2023-26122
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAll versions of the package safe-eval are vulnerable to Sandbox Bypass due to improper input sanitization. The vulnerability is derived from prototype pollution exploitation. Exploiting this vulnerability might result in remote code execution ("RCE"). **Vulnerable functions:** __defineGetter__, stack(), toLocaleString(), propertyIsEnumerable.call(), valueOf().
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe safe-eval package contains a sandbox bypass vulnerability allowing attackers to escape the JavaScript sandbox through prototype pollution via improper input sanitization. Exploitation leverages vulnerable functions including __defineGetter__, stack(), toLocaleString(), propertyIsEnumerable.call(), and valueOf() to achieve arbitrary code execution on the host system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify safe-eval in dependenciesRun 'npm list safe-eval' or check package.json for 'safe-eval' in dependencies, devDependencies, or resolutions sectionsAffected if safe-eval appears in any dependencies section
-
Check installed versionRun 'npm list safe-eval' and compare the version number to <= 0.4.1Affected if The installed version is 0.4.1 or lower
-
Verify safe-eval is actively usedSearch codebase for require('safe-eval') or import statements loading the package, then trace if the returned function processes any inputAffected if Code calls safe-eval() with data that originates from untrusted sources such as HTTP requests, user uploads, or external APIs
-
Check for prototype pollution attack surfaceReview code paths where safe-eval processes input containing object literals or keys like __defineGetter__, __proto__, or constructorAffected if User-controllable data reaches safe-eval in contexts that could include the vulnerable functions (toLocaleString, valueOf, propertyIsEnumerable.call, stack)
-
Audit input sanitizationExamine code between user input and safe-eval call to determine if sanitization or validation is appliedAffected if No sanitization exists on data passed to safe-eval, or sanitization can be bypassed
You are affected if safe-eval version 0.4.1 or lower is installed and your code passes untrusted input directly to safe-eval without effective sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately cease use of safe-eval as the package is unmaintained with no patch available; migrate to a properly maintained sandboxing solution such as the native Node.js vm module with strict configuration or a vetted alternative like vm2 (with current patches applied).
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26122 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-26122 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data