Cyber Resilience

CVE-2023-26122

Safe-Eval Project Safe-Eval ≤ 0.4.1

Public PoC
Published
11 April 2023
Modified
07 February 2025
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.021 80th percentile
Risk Priority 72 floored blend · peak EPSS

Summary

CVE-2023-26122 is a high-severity Prototype Pollution (CWE-1321) vulnerability in Safe-Eval Project Safe-Eval. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 20% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The package safe-eval is affected by CVE-2023-26122, a sandbox bypass vulnerability present in all versions due to improper input sanitization stemming from prototype pollution. This issue impacts functions including __defineGetter__, stack(), toLocaleString(), propertyIsEnumerable.call(), and valueOf(), and carries a CVSS score of 8.8.

An attacker with low privileges can exploit the vulnerability over the network without user interaction to achieve remote code execution by bypassing the intended sandbox restrictions.

The EPSS score for this CVE stands at 0.0808 with no increase from its peak value. References point to GitHub issues and a gist detailing the problem.

EU & UK References

Vulnerability Data

All 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(),…

more

valueOf().

CWE(s)
CWE-265CWE-1321

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-26121Same product: Safe-Eval Project Safe-Eval
CVE-2026-33672Shared CWE-1321
CVE-2024-39018Shared CWE-1321
CVE-2026-46510Shared CWE-1321
CVE-2024-36578Shared CWE-1321
CVE-2019-0230Shared CWE-1321
CVE-2026-34621Shared CWE-1321
CVE-2025-3193Shared CWE-1321
CVE-2024-36580Shared CWE-1321
CVE-2025-54803Shared CWE-1321

Affected Assets

safe-eval project
safe-eval
≤ 0.4.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.3.6

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches prototype-pollution flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.

A.8.32 Change management partial match
prevents

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References