{"answers":{"affected":"2 open source packages ship an affected version, including set-in. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26021 exists.","fix":"Upgrade set-in to 2.0.5 or later.","what":"CVE-2026-26021 is a critical code injection vulnerability in ahdinosaur set-in, published on 11 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-26021 and fix it if it is affected.\n\nWhat it is: CVE-2026-26021 is a critical code injection vulnerability in ahdinosaur set-in, published on 11 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26021 exists.\n\nAffected packages and fixed versions:\n- set-in (npm): affected from 2.0.1; fixed in 2.0.5\n- set-in (npm): affected from 2.0.1; fixed in 2.0.5\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-26021/ (Markdown: https://insights.sbomify.com/CVE-2026-26021/index.md)","id":"CVE-2026-26021","markdown":"https://insights.sbomify.com/CVE-2026-26021/index.md","name":"CVE-2026-26021","record":{"aliases":["GHSA-2c4m-g7rx-63q7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"npm JavaScript library","requires_auth":"none","summary":"Prototype pollution in set-in allows attackers to modify Object.prototype via crafted input, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"set-in","vendor":"set-in_project"}],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"set-in provides the set value of nested associative structure given array of keys. A prototype pollution vulnerability exists in the the npm package set-in (\u003e=2.0.1, \u003c 2.0.5). Despite a previous fix that attempted to mitigate prototype pollution by checking whether user input contained a forbidden key, it is still possible to pollute Object.prototype via a crafted input using Array.prototype. This has been fixed in version 2.0.5.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Prototype pollution in set-in","id":"CVE-2026-26021","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Gogs: Stored XSS via data URI in issue comments","id":"CVE-2026-26022"},"packages":[{"ecosystem":"npm","fixed":["2.0.5"],"introduced":["2.0.1"],"last_affected":[],"package":"set-in","purl":null,"source":"GHSA-2c4m-g7rx-63q7"},{"ecosystem":"npm","fixed":["2.0.5"],"introduced":["2.0.1"],"last_affected":[],"package":"set-in","purl":"pkg:npm/set-in","source":"GHSA-2c4m-g7rx-63q7"}],"prev":{"headline":"AutoGPT Affected by Remote Code Execution via Dynamic Module Import in Block Loading (__import__)","id":"CVE-2026-26020"},"products":["set-in"],"published":"2026-02-11","related":[{"cvss_score":9.8,"headline":"Prototype pollution in set-in","id":"CVE-2020-28273","kev_date_added":null,"published":"2020-12-02"},{"cvss_score":8.6,"headline":"Prototype Pollution","id":"CVE-2022-25354","kev_date_added":null,"published":"2022-03-17"}],"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":"2026-02-12","vendors":["ahdinosaur"]},"summary":"Prototype pollution in set-in allows attackers to modify Object.prototype via crafted input, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-26021/"}