<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 08:15:18 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2025-66219</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2025-66219</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2025-66219</guid>
    </item>
    <item>
      <title>GHSA-j9wj-m24m-7jj6 — willitmerge has a Command Injection vulnerability</title>
      <link>https://db.gcve.eu/vuln/ghsa-j9wj-m24m-7jj6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: willitmerge&lt;/p&gt;
&lt;p&gt;willitmerge describes itself as a command line tool to check if pull requests are mergeable. There is a Command Injection vulnerability in version `willitmerge@0.2.1`.&lt;/p&gt;
&lt;p&gt;Resources: 
 * Project&amp;#39;s GitHub source code: https://github.com/shama/willitmerge/
 * Project&amp;#39;s npm package: https://www.npmjs.com/package/willitmerge&lt;/p&gt;
&lt;p&gt;## Background on exploitation&lt;/p&gt;
&lt;p&gt;Reporting a Command Injection vulnerability in `willitmerge` npm package.&lt;/p&gt;
&lt;p&gt;A security vulnerability manifests in this package due to the use of insecure child process execution API (`exec`) to which it concateanes user input, whether provided to the command-line flag, or is in user control in the target repository.&lt;/p&gt;
&lt;p&gt;## Exploit&lt;/p&gt;
&lt;p&gt;### POC 1&lt;/p&gt;
&lt;p&gt;1. Install `willitmerge`
2. Run it with the following command&lt;/p&gt;
&lt;p&gt;```sh
willitmerge --verbose --remote &amp;#34;https://github.com/lirantal/npq.git; touch /tmp/hel&amp;#34;
```&lt;/p&gt;
&lt;p&gt;3. Confirm the file `/tmp/hel` is created on disk&lt;/p&gt;
&lt;p&gt;### GitHub-sourced attack vector&lt;/p&gt;
&lt;p&gt;[Lines 189-197](https://github.com/shama/willitmerge/blob/2fe91d05191fb05ac6da685828d109a3a5885028/lib/willitmerge.js#L189-L197) in `lib/willitmerge.js`
pass user input controlled by repository collaborators into the git command:&lt;/p&gt;
&lt;p&gt;```js
  var cmds = [
    &amp;#39;git checkout -b &amp;#39; + branch + &amp;#39; &amp;#39; + that.options.remote + &amp;#39;/&amp;#39; + iss.base.ref,
    &amp;#39;git remote add &amp;#39; + branch + &amp;#39; &amp;#39; + gitUrl,
    &amp;#39;git pull &amp;#39; + branch + &amp;#39; &amp;#39; + iss.head.ref,
    &amp;#39;git reset --merge HEAD&amp;#39;,
    &amp;#39;git checkout &amp;#39; + origBranch,
    &amp;#39;git branch -D &amp;#39; + branch,
    &amp;#39;git remote rm &amp;#39; + branch
  ];
```…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: willitmerge&lt;/p&gt;
&lt;p&gt;willitmerge describes itself as a command line tool to check if pull requests are mergeable. There is a Command Injection vulnerability in version `willitmerge@0.2.1`.&lt;/p&gt;
&lt;p&gt;Resources: 
 * Project&amp;#39;s GitHub source code: https://github.com/shama/willitmerge/
 * Project&amp;#39;s npm package: https://www.npmjs.com/package/willitmerge&lt;/p&gt;
&lt;p&gt;## Background on exploitation&lt;/p&gt;
&lt;p&gt;Reporting a Command Injection vulnerability in `willitmerge` npm package.&lt;/p&gt;
&lt;p&gt;A security vulnerability manifests in this package due to the use of insecure child process execution API (`exec`) to which it concateanes user input, whether provided to the command-line flag, or is in user control in the target repository.&lt;/p&gt;
&lt;p&gt;## Exploit&lt;/p&gt;
&lt;p&gt;### POC 1&lt;/p&gt;
&lt;p&gt;1. Install `willitmerge`
2. Run it with the following command&lt;/p&gt;
&lt;p&gt;```sh
willitmerge --verbose --remote &amp;#34;https://github.com/lirantal/npq.git; touch /tmp/hel&amp;#34;
```&lt;/p&gt;
&lt;p&gt;3. Confirm the file `/tmp/hel` is created on disk&lt;/p&gt;
&lt;p&gt;### GitHub-sourced attack vector&lt;/p&gt;
&lt;p&gt;[Lines 189-197](https://github.com/shama/willitmerge/blob/2fe91d05191fb05ac6da685828d109a3a5885028/lib/willitmerge.js#L189-L197) in `lib/willitmerge.js`
pass user input controlled by repository collaborators into the git command:&lt;/p&gt;
&lt;p&gt;```js
  var cmds = [
    &amp;#39;git checkout -b &amp;#39; + branch + &amp;#39; &amp;#39; + that.options.remote + &amp;#39;/&amp;#39; + iss.base.ref,
    &amp;#39;git remote add &amp;#39; + branch + &amp;#39; &amp;#39; + gitUrl,
    &amp;#39;git pull &amp;#39; + branch + &amp;#39; &amp;#39; + iss.head.ref,
    &amp;#39;git reset --merge HEAD&amp;#39;,
    &amp;#39;git checkout &amp;#39; + origBranch,
    &amp;#39;git branch -D &amp;#39; + branch,
    &amp;#39;git remote rm &amp;#39; + branch
  ];
```…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-j9wj-m24m-7jj6</guid>
    </item>
  </channel>
</rss>
