# CVE-2025-66219: willitmerge has a command Injection vulnerability

> An attacker can execute arbitrary commands via insecure child process execution in the willitmerge CLI tool.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-j9wj-m24m-7jj6

## What is CVE-2025-66219?

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.

### Official 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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-66219?

2 open source packages ship an affected version, including willitmerge. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `willitmerge` | npm | All versions to 0.2.1 | None |
| `willitmerge` | npm | All versions to 0.2.1 | None |

Products: Dontkry Willitmerge.

## How do I fix CVE-2025-66219?

No fix has been published for CVE-2025-66219 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-66219 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66219 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66219 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66219 exists.

Affected packages and fixed versions:
- willitmerge (npm): affected all versions up to 0.2.1; no fix listed
- willitmerge (npm): affected all versions up to 0.2.1; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-66219/ (Markdown: https://insights.sbomify.com/CVE-2025-66219/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-66219
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-66219
- OSV: https://osv.dev/vulnerability/CVE-2025-66219

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-66219/
Summaries are generated and may contain mistakes; the official description above is the record.