<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 16:05:16 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-100369</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-100369</link>
      <description>&lt;p&gt;CliInvoke and its formerly named `AlastairLundy.CliInvoke` package are .NET libraries for invoking command-line programs and wrapping executable processes. `CliInvoke` versions 2.0.0 through 2.8.4, 2.9.0 through 2.9.3, 2.10.0 through 2.10.4, and 3.0.0-alpha.1 through 3.0.0-beta.1, as well as `AlastairLundy.CliInvoke` versions 2.0.0-alpha.1 through 2.0.0, contain an argument-injection vulnerability in `RunnerProcessFactory` on the 2.x line and `RunnerConfigurationFactory` on the 3.x line. These factories combine runner arguments, a caller-controlled target, and caller-controlled arguments into one `ProcessStartInfo.Arguments` string, allowing a double quote in the target or an argument to terminate an operating-system-level quoted region and inject unintended elements into the runner’s argument vector, potentially resulting in arbitrary command execution when a shell runner is used. The vulnerability is patched in `CliInvoke` versions 2.8.5, 2.9.4, 2.10.5, and 3.0.0-beta.2, and in `AlastairLundy.CliInvoke` version 2.0.2. No complete workaround is available; users unable to upgrade can partially mitigate the issue by removing double quotes from targets and arguments, additionally removing shell metacharacters when using shell runners, or bypassing the vulnerable factory and constructing a `ProcessConfiguration` with an explicit `ArgumentList`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;CliInvoke and its formerly named `AlastairLundy.CliInvoke` package are .NET libraries for invoking command-line programs and wrapping executable processes. `CliInvoke` versions 2.0.0 through 2.8.4, 2.9.0 through 2.9.3, 2.10.0 through 2.10.4, and 3.0.0-alpha.1 through 3.0.0-beta.1, as well as `AlastairLundy.CliInvoke` versions 2.0.0-alpha.1 through 2.0.0, contain an argument-injection vulnerability in `RunnerProcessFactory` on the 2.x line and `RunnerConfigurationFactory` on the 3.x line. These factories combine runner arguments, a caller-controlled target, and caller-controlled arguments into one `ProcessStartInfo.Arguments` string, allowing a double quote in the target or an argument to terminate an operating-system-level quoted region and inject unintended elements into the runner’s argument vector, potentially resulting in arbitrary command execution when a shell runner is used. The vulnerability is patched in `CliInvoke` versions 2.8.5, 2.9.4, 2.10.5, and 3.0.0-beta.2, and in `AlastairLundy.CliInvoke` version 2.0.2. No complete workaround is available; users unable to upgrade can partially mitigate the issue by removing double quotes from targets and arguments, additionally removing shell metacharacters when using shell runners, or bypassing the vulnerable factory and constructing a `ProcessConfiguration` with an explicit `ArgumentList`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-100369</guid>
    </item>
    <item>
      <title>GHSA-j73w-8hfr-4gc9 — CliInvoke: Argument Injection in Extensibility Runner Factory</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-j73w-8hfr-4gc9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NuGet: CliInvoke, NuGet: AlastairLundy.CliInvoke&lt;/p&gt;
&lt;p&gt;### Impact
An argument-injection vulnerability exists in the `CliInvoke`
package&amp;#39;s runner factory: `RunnerProcessFactory` on the 2.x line and
`RunnerConfigurationFactory` on the 3.x line.&lt;/p&gt;
&lt;p&gt;The factory joins the runner arguments, the caller&amp;#39;s target, and the
caller&amp;#39;s arguments into a single `ProcessStartInfo.Arguments` string and
hands it to the OS. The OS command-line parser re-tokenizes the string
before the runner sees it. A double quote (`&amp;#34;`) in the target or in any
argument closes the OS-level quoted region and lets the next character
enter argv as a separate element.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to:&lt;/p&gt;
&lt;p&gt;- **2.8.5** (2.8.x line)
- **2.9.4** (2.9.x line)
- **2.10.5** (2.10.x line)
- **3.0.0-beta.2** (3.x pre-release line)&lt;/p&gt;
&lt;p&gt;### Workarounds
No complete workaround is available. Until you can upgrade:&lt;/p&gt;
&lt;p&gt;- Strip `&amp;#34;` from any target or argument before passing it to the
  factory. On shell runners, also strip `;`, `|`, `&amp;amp;`, `$`, backtick,
  and parentheses.
- Or bypass the factory entirely and build the `ProcessConfiguration`
  directly. Set `ArgumentList` explicitly to the argv you want the
  runner to receive.&lt;/p&gt;
&lt;p&gt;These are partial mitigations. They shift the quoting problem to your
code.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NuGet: CliInvoke, NuGet: AlastairLundy.CliInvoke&lt;/p&gt;
&lt;p&gt;### Impact
An argument-injection vulnerability exists in the `CliInvoke`
package&amp;#39;s runner factory: `RunnerProcessFactory` on the 2.x line and
`RunnerConfigurationFactory` on the 3.x line.&lt;/p&gt;
&lt;p&gt;The factory joins the runner arguments, the caller&amp;#39;s target, and the
caller&amp;#39;s arguments into a single `ProcessStartInfo.Arguments` string and
hands it to the OS. The OS command-line parser re-tokenizes the string
before the runner sees it. A double quote (`&amp;#34;`) in the target or in any
argument closes the OS-level quoted region and lets the next character
enter argv as a separate element.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to:&lt;/p&gt;
&lt;p&gt;- **2.8.5** (2.8.x line)
- **2.9.4** (2.9.x line)
- **2.10.5** (2.10.x line)
- **3.0.0-beta.2** (3.x pre-release line)&lt;/p&gt;
&lt;p&gt;### Workarounds
No complete workaround is available. Until you can upgrade:&lt;/p&gt;
&lt;p&gt;- Strip `&amp;#34;` from any target or argument before passing it to the
  factory. On shell runners, also strip `;`, `|`, `&amp;amp;`, `$`, backtick,
  and parentheses.
- Or bypass the factory entirely and build the `ProcessConfiguration`
  directly. Set `ArgumentList` explicitly to the argv you want the
  runner to receive.&lt;/p&gt;
&lt;p&gt;These are partial mitigations. They shift the quoting problem to your
code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-j73w-8hfr-4gc9</guid>
    </item>
  </channel>
</rss>
