nuget package report

Is AlastairLundy.CliInvoke safe?

1 known vulnerability, worst severity HIGH.

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so nuget packages are not covered.


      cvss
      0.0
      high

      severity band, no base score published

      epss
      not scored

      chance of exploitation in 30 days

      xyz score
      not scored

      CyberXYZ composite out of 10

      fig. 01 — GHSA-j73w-8hfr-4gc9, the advisory selected below

      // 1 advisories

      GHSA-j73w-8hfr-4gc9

      HIGHCVE-2026-100369
      // impact

      An argument-injection vulnerability exists in the CliInvoke package's runner factory: RunnerProcessFactory on the 2.x line and RunnerConfigurationFactory on the 3.x line.

      The factory joins the runner arguments, the caller's target, and the caller'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 (") in the target or in any argument closes the OS-level quoted region and lets the next character enter argv as a separate element.

      // patches

      Upgrade to:

      • 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)
      // workarounds

      No complete workaround is available. Until you can upgrade:

      • Strip " from any target or argument before passing it to the

      factory. On shell runners, also strip ;, |, &, $, 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.

      These are partial mitigations. They shift the quoting problem to your code.


      Checked 2026-09-26 at 01:04 UTC. The most recent advisory here was published 2026-09-25. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.