# CVE-2022-30580: Empty Cmd.Path can trigger unintended binary in os/exec on Windows

> Attackers can execute arbitrary binaries from the working directory if Cmd.Path is unset in Go's os/exec package on Windows.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Aug 2022
- **Updated:** 6 Mar 2026
- **Also known as:** AZL-10532, AZL-79108, AZL-98856, BIT-golang-2022-30580, GHSA-2v97-2cxm-mvp4, GO-2022-0532

## What is CVE-2022-30580?

CVE-2022-30580 is a high-severity code injection vulnerability in Golang Go, published on 9 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Code injection in Cmd.Start in os/exec before Go 1.17.11 and Go 1.18.3 allows execution of any binaries in the working directory named either "..com" or "..exe" by calling Cmd.Run, Cmd.Start, Cmd.Output, or Cmd.CombinedOutput when Cmd.Path is unset.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-30580?

2 open source packages ship an affected version, including golang and stdlib. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang` | Bitnami | All versions | 1.17.11, 1.18.3 |
| `stdlib` | Go | All versions | 1.17.11, 1.18.3 |

Products: Golang Go.

## How do I fix CVE-2022-30580?

Upgrade golang to a fixed version for your release line: 1.17.11 or 1.18.3.

## Is CVE-2022-30580 being exploited?

There is no known exploitation of CVE-2022-30580 in the wild and no public exploit code.

## Other vulnerabilities in Golang Go

- [CVE-2020-0601](https://insights.sbomify.com/CVE-2020-0601/): Microsoft Windows CryptoAPI Spoofing (high 8.1, exploited in the wild)
- [CVE-2026-27143](https://insights.sbomify.com/CVE-2026-27143/): Missing bound checks can lead to memory corruption in safe Go in cmd/compile (critical 9.8)
- [CVE-2024-24790](https://insights.sbomify.com/CVE-2024-24790/): Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses in net/netip (critical 9.8)
- [CVE-2023-39320](https://insights.sbomify.com/CVE-2023-39320/): Arbitrary code execution via go.mod toolchain directive in cmd/go (critical 9.8)
- [CVE-2023-24540](https://insights.sbomify.com/CVE-2023-24540/): Improper handling of JavaScript whitespace in html/template (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-30580 and fix it if it is affected.

What it is: CVE-2022-30580 is a high-severity code injection vulnerability in Golang Go, published on 9 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30580 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang (Bitnami): affected all versions; fixed in 1.17.11, 1.18.3
- stdlib (Go): affected all versions; fixed in 1.17.11, 1.18.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-30580/ (Markdown: https://insights.sbomify.com/CVE-2022-30580/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-30580
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-30580
- OSV: https://osv.dev/vulnerability/CVE-2022-30580

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-30580/
Summaries are generated and may contain mistakes; the official description above is the record.