{"answers":{"affected":"2 open source packages ship an affected version, including @nyariv/sandboxjs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25142 in the wild and no public exploit code.","fix":"Upgrade @nyariv/sandboxjs to 0.8.27 or later.","what":"CVE-2026-25142 is a critical code injection vulnerability in nyariv SandboxJS, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25142 and fix it if it is affected.\n\nWhat it is: CVE-2026-25142 is a critical code injection vulnerability in nyariv SandboxJS, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25142 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @nyariv/sandboxjs (npm): affected all versions; fixed in 0.8.27\n- @nyariv/sandboxjs (npm): affected all versions; fixed in 0.8.27\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-2026-25142/ (Markdown: https://insights.sbomify.com/CVE-2026-25142/index.md)","id":"CVE-2026-25142","markdown":"https://insights.sbomify.com/CVE-2026-25142/index.md","name":"CVE-2026-25142","record":{"aliases":["GHSA-9p4w-fq8m-2hp7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript sandboxing library","requires_auth":"none","summary":"Attackers can escape the SandboxJS sandbox and execute arbitrary code via prototype pollution using __lookupGetter__.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sandboxjs","vendor":"nyariv"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"},{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"SandboxJS is a JavaScript sandboxing library. Prior to 0.8.27, SanboxJS does not properly restrict __lookupGetter__ which can be used to obtain prototypes, which can be used for escaping the sandbox / remote code execution. This vulnerability is fixed in 0.8.27.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SandboxJS Prototype Pollution -\u003e Sandbox Escape -\u003e RCE","id":"CVE-2026-25142","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"melange affected by potential host command execution via license-check YAML mode patch pipeline","id":"CVE-2026-25143"},"packages":[{"ecosystem":"npm","fixed":["0.8.27"],"introduced":["0"],"last_affected":[],"package":"@nyariv/sandboxjs","purl":null,"source":"GHSA-9p4w-fq8m-2hp7"},{"ecosystem":"npm","fixed":["0.8.27"],"introduced":["0"],"last_affected":[],"package":"@nyariv/sandboxjs","purl":"pkg:npm/%40nyariv/sandboxjs","source":"GHSA-9p4w-fq8m-2hp7"}],"prev":{"headline":"Orval has a code injection via unsanitized x-enum-descriptions uing JS comments","id":"CVE-2026-25141"},"products":["SandboxJS"],"published":"2026-02-02","related":[{"cvss_score":10,"headline":"SandboxJS: Sandbox escape via Function.caller leakage of internal call op","id":"CVE-2026-43898","kev_date_added":null,"published":"2026-05-28"},{"cvss_score":10,"headline":"SandboxJS: Sandbox integrity escape","id":"CVE-2026-34208","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":10,"headline":"SandboxJS has a Sandbox Escape","id":"CVE-2026-26954","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":10,"headline":"SandboxJS has a Sandbox Escape","id":"CVE-2026-25520","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":10,"headline":"SandboxJS has a Sandbox Escape via Prototype Whitelist Bypass and Host Prototype Pollution","id":"CVE-2026-25586","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":10,"headline":"SandboxJS has a Sandbox Escape","id":"CVE-2026-25587","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":10,"headline":"SandboxJS has a sandbox escape via TOCTOU bug on keys in property accesses","id":"CVE-2026-25641","kev_date_added":null,"published":"2026-02-06"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-04","vendors":["nyariv"]},"summary":"Attackers can escape the SandboxJS sandbox and execute arbitrary code via prototype pollution using __lookupGetter__.","url":"https://insights.sbomify.com/CVE-2026-25142/"}