dbcve.org
WillitmergeApplication · Dontkry

CVE-2025-66219

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-29
Fix available
A fix is available. Upgrade to after 0.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Command injection vulnerability in willitmerge versions 0.2.1 and prior where user input from CLI flags or repository data is concatenated directly into commands executed via the insecure exec API, allowing arbitrary shell command execution.

MitigationUntil an official patch is released, avoid using willitmerge or strictly sandbox its execution environment; review code to identify all exec calls and replace with safe subprocess APIs (spawn with argument arrays) after proper input validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WillitmergeApplication
Affected:<= 0.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if willitmerge is installed
    Run 'pip show willitmerge' or check your package manager for the installed version of willitmerge
    Affected if The installed version is 0.2.1 or lower, or no version is shown but the package is present
  2. Locate the willitmerge executable or entry point
    Run 'which willitmerge' on Linux/macOS or where it is invoked from in your workflow
    Affected if The tool is accessible in your PATH and is version 0.2.1 or prior
  3. Inspect how the tool is invoked in your environment
    Review any scripts, CI/CD pipelines, or automation that call willitmerge and check if command-line flags are passed with user-supplied values
    Affected if User-controlled data from external sources is passed as arguments to willitmerge
  4. Examine the exec API usage in the source code
    If you have access to the source code, search for usages of os.system, subprocess.call with shell=True, or exec() that concatenate user input into command strings
    Affected if The code directly interpolates user input into command strings passed to exec or similar APIs without sanitization
  5. Determine if target repositories contain user-controlled data
    Assess whether willitmerge operates on repositories where branch names, commit messages, or other git data can be influenced by untrusted users
    Affected if Willitmerge processes data from untrusted or public repositories

You are affected if willitmerge version 0.2.1 or lower is installed and processes any user-supplied input via command-line flags or repository data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.2.1
Interim mitigation

Until an official patch is released, avoid using willitmerge or strictly sandbox its execution environment; review code to identify all exec calls and replace with safe subprocess APIs (spawn with argument arrays) after proper input validation.

Recommended fix High confidence
  1. No remediation steps available - the official description states 'At time of publication, no known fix is public'
  2. Monitor the project's GitHub repository (github.com) for security advisories and release announcements
  3. Consider alternative tools or manual processes for checking pull request mergeability until a fix is released

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Willitmerge Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66219 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data