willitmerge has a command Injection vulnerability
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
willitmerge CLI tool versions ≤0.2.1 have a command injection vulnerability due to unsafe exec() usage with user-controllable input.
Vulnerability
Overview
willitmerge is a Node.js command-line tool that checks if GitHub pull requests are mergeable. In versions 0.2.1 and prior, it uses the insecure child_process.exec() API, directly concatenating user-supplied input into shell commands. This input can come from command-line flags such as --remote or from repository metadata (e.g., branch names, remote URLs) that are under user control [1][3].
Exploitation
Vector
An attacker can exploit this vulnerability by providing malicious data to the --remote flag or by creating a repository with crafted branch names. For example, a proof-of-concept runs willitmerge --verbose --remote "https://github.com/lirantal/npq.git; touch /tmp/hel", which executes the injected touch command on the host [4]. Similarly, a malicious branch name like ;{echo,hello,world}>/tmp/c can be used because the tool concatenates such names directly into git commands without sanitization [3].
Impact
Successful exploitation allows arbitrary command execution with the privileges of the user running willitmerge. This can lead to unauthorized file access, persistence, lateral movement, or full system compromise, depending on the environment [1][4].
Mitigation
Status
As of the publication date, no fix is available for this vulnerability [1][4]. Users are advised to avoid using willitmerge with untrusted input or in automated pipelines where the tool processes repositories from unverified sources. No official workaround or patch has been released.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
willitmergenpm | <= 0.2.1 | — |
Affected products
1- shama/willitmergev5Range: <= 0.2.1
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
4- github.com/advisories/GHSA-j9wj-m24m-7jj6ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2025-66219ghsaADVISORY
- github.com/shama/willitmerge/blob/2fe91d05191fb05ac6da685828d109a3a5885028/lib/willitmerge.jsghsax_refsource_MISCWEB
- github.com/shama/willitmerge/security/advisories/GHSA-j9wj-m24m-7jj6ghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.