{"answers":{"affected":"2 open source packages ship an affected version, including safe-eval. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26122 exists.","fix":"No fix has been published for CVE-2023-26122 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-26122 is a high-severity code injection vulnerability in safe-eval, published on 11 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-26122 and fix it if it is affected.\n\nWhat it is: CVE-2023-26122 is a high-severity code injection vulnerability in safe-eval, published on 11 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26122 exists.\n\nAffected packages and fixed versions:\n- safe-eval (npm): affected all versions up to 0.4.2; no fix listed\n- safe-eval (npm): affected all versions up to 0.4.2; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-26122/ (Markdown: https://insights.sbomify.com/CVE-2023-26122/index.md)","id":"CVE-2023-26122","markdown":"https://insights.sbomify.com/CVE-2023-26122/index.md","name":"CVE-2023-26122","record":{"aliases":["GHSA-79xf-67r4-q2jj"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript sandbox library","requires_auth":"low_privilege","summary":"Attackers can bypass the safe-eval sandbox via prototype pollution to achieve remote code execution in applications using this library.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"safe-eval","vendor":"safe-eval_project"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"},{"id":"CWE-265","name":null}],"description":"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.\rExploiting this vulnerability might result in remote code execution (\"RCE\").\r\r**Vulnerable functions:**\r\r__defineGetter__, stack(), toLocaleString(), propertyIsEnumerable.call(),  valueOf().","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"safe-eval vulnerable to Sandbox Bypass due to improper input sanitization","id":"CVE-2023-26122","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2023"},"n_packages":2,"n_references":8,"next":{"headline":"Cross-site scripting in raysan5/raylib","id":"CVE-2023-26123"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.4.2"],"package":"safe-eval","purl":null,"source":"GHSA-79xf-67r4-q2jj"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.4.2"],"package":"safe-eval","purl":"pkg:npm/safe-eval","source":"GHSA-79xf-67r4-q2jj"}],"prev":{"headline":"safe-eval vulnerable to Prototype Pollution via the safeEval function","id":"CVE-2023-26121"},"products":["safe-eval"],"published":"2023-04-11","related":[{"cvss_score":10,"headline":"Sandbox Breakout in safe-eval","id":"CVE-2017-16088","kev_date_added":null,"published":"2018-06-07"},{"cvss_score":8.1,"headline":"Sandbox Escape","id":"CVE-2020-7710","kev_date_added":null,"published":"2020-08-21"},{"cvss_score":7.5,"headline":"safe-eval vulnerable to Prototype Pollution via the safeEval function","id":"CVE-2023-26121","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":7.5,"headline":"Prototype Pollution","id":"CVE-2022-25904","kev_date_added":null,"published":"2022-12-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-07","vendors":["n/a"]},"summary":"Attackers can bypass the safe-eval sandbox via prototype pollution to achieve remote code execution in applications using this library.","url":"https://insights.sbomify.com/CVE-2023-26122/"}