{"answers":{"affected":"2 open source packages ship an affected version, including willitmerge. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66219 exists.","fix":"No fix has been published for CVE-2025-66219 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66219 is a medium-severity command injection vulnerability in shama willitmerge, published on 29 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66219 and fix it if it is affected.\n\nWhat it is: CVE-2025-66219 is a medium-severity command injection vulnerability in shama willitmerge, published on 29 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66219 exists.\n\nAffected packages and fixed versions:\n- willitmerge (npm): affected all versions up to 0.2.1; no fix listed\n- willitmerge (npm): affected all versions up to 0.2.1; 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-2025-66219/ (Markdown: https://insights.sbomify.com/CVE-2025-66219/index.md)","id":"CVE-2025-66219","markdown":"https://insights.sbomify.com/CVE-2025-66219/index.md","name":"CVE-2025-66219","record":{"aliases":["GHSA-j9wj-m24m-7jj6"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"npm CLI tool","requires_auth":"none","summary":"An attacker can execute arbitrary commands via insecure child process execution in the willitmerge CLI tool.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"willitmerge","vendor":"dontkry"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"willitmerge is a command line tool to check if pull requests are mergeable. In versions 0.2.1 and prior, there is a command Injection vulnerability in willitmerge. The vulnerability manifests in this package due to the use of insecure child process execution API (exec) to which it concatenates user input, whether provided to the command-line flag, or is in user control in the target repository. At time of publication, no known fix is public.","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":"willitmerge has a command Injection vulnerability","id":"CVE-2025-66219","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Envoy's TLS certificate matcher for `match_typed_subject_alt_names` may incorrectly treat certificates containing an embedded null byte","id":"CVE-2025-66220"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.2.1"],"package":"willitmerge","purl":null,"source":"GHSA-j9wj-m24m-7jj6"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.2.1"],"package":"willitmerge","purl":"pkg:npm/willitmerge","source":"GHSA-j9wj-m24m-7jj6"}],"prev":{"headline":"AIS-catcher Integer Underflow in MQTT Packet Parsing leading to Heap Buffer Overflow","id":"CVE-2025-66217"},"products":["willitmerge"],"published":"2025-11-29","related":[],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-01","vendors":["shama"]},"summary":"An attacker can execute arbitrary commands via insecure child process execution in the willitmerge CLI tool.","url":"https://insights.sbomify.com/CVE-2025-66219/"}