All reports
Unknown

Empty Cmd.Path can trigger unintended binary in os/exec on Windows

Affected versions

Affected versions
<1.17.11 || >=1.18.0-0 <1.18.3
Fixed version
1.17.11 · 1.18.3

Exploitation

CVE-2022-30580

Probability of exploitation in the next 30 days: 0.70%

FIRST EPSS · 2026-11-21

Description

On Windows, executing Cmd.Run, Cmd.Start, Cmd.Output, or Cmd.CombinedOutput when Cmd.Path is unset will unintentionally trigger execution of any binaries in the working directory named either "..com" or "..exe".

Links

Credits

  • Chris Darroch (chrisd8088@github.com)
  • brian m. carlson (bk2204@github.com)
  • Mikhail Shcherbakov (https://twitter.com/yu5k3)