Skip to content
Fencer Intel
high 7.5

CVE-2023-26121 json

safe-eval vulnerable to Prototype Pollution via the safeEval function

published 3y ago modified 4mo ago also GHSA-hcg3-56jf-x4vh , EUVD-2023-1322

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

All versions of the package safe-eval are vulnerable to Prototype Pollution via the safeEval function, due to improper sanitization of its parameter content.

Is CVE-2023-26121 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-15).

Exploits and checks

  • security.snyk.io https://security.snyk.io/vuln/SNYK-JS-SAFEEVAL-3373062 referenced PoC, tagged "exploit" by a source, unverified
  • gist.github.com https://gist.github.com/seongil-wi/9d9fc0cc5b7b130419cd45827e59c4f9 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/hacksparrow/safe-eval/issues/28 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm safe-eval
<=0.4.2
no fix listed

Affected products

  • n/a safe-eval

Classification

Weakness
  • CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.