# CVE-2025-22867: Arbitrary code execution during build on darwin in cmd/go

> Attackers can execute arbitrary code during Go module builds on macOS if CGO directives use specific linker path values.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2025
- **Updated:** 6 Feb 2025
- **Also known as:** BIT-golang-2025-22867, ECHO-d085-1c12-aa45, GHSA-664g-9vm2-r26f, GO-2025-3428

## What is CVE-2025-22867?

CVE-2025-22867 is a high-severity code injection vulnerability in cmd/go, published on 6 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Darwin, building a Go module which contains CGO can trigger arbitrary code execution when using the Apple version of ld, due to usage of the @executable_path, @loader_path, or @rpath special values in a "#cgo LDFLAGS" directive. This issue only affected go1.24rc2.

## Which versions are affected by CVE-2025-22867?

2 open source packages ship an affected version, including golang and toolchain.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang` | Bitnami | From 1.24.0-rc.2 | 1.24.0-rc.3 |
| `toolchain` | Go | From 1.24.0-rc.2 | 1.24.0-rc.3 |

## How do I fix CVE-2025-22867?

Upgrade golang to 1.24.0-rc.3 or later.

## Is CVE-2025-22867 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22867 and fix it if it is affected.

What it is: CVE-2025-22867 is a high-severity code injection vulnerability in cmd/go, published on 6 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-22867 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang (Bitnami): affected from 1.24.0-rc.2; fixed in 1.24.0-rc.3
- toolchain (Go): affected from 1.24.0-rc.2; fixed in 1.24.0-rc.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-2025-22867/ (Markdown: https://insights.sbomify.com/CVE-2025-22867/index.md)
```

## Sources

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

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