Skip to main content
VulnerabilityPublished Updated

CVE-2025-66219: willitmerge has a Command Injection vulnerability

Affects willitmergeSource GCVE Database

0
Compare
Authoritative record:CVE-2025-66219· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium.

Data as of 20 Nov 2026, 01:47 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
npmwillitmergeAffected
  • <=0.2.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should avoid using willitmerge version 0.2.1 with untrusted inputs or in environments where malicious repository data could be supplied. Monitor the project's repository and npm package for updates addressing this issue. Until a fix is released, do not run willitmerge on untrusted repositories or inputs that could be manipulated by attackers.

Description

willitmerge version 0.2.1 contains a command injection vulnerability due to unsafe concatenation of user input into shell commands executed via the child process exec API. This flaw allows an attacker to execute arbitrary commands on the host system by crafting malicious input such as repository URLs or branch names. The vulnerability arises from passing user-controlled data directly into git commands without proper sanitization.

References

Community reviews

Loading reviews…