# CVE-2026-97036: Arbitrary code execution during build on darwin via "-l to_library" in cgo in cmd/go


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-97036, GHSA-qxq7-88pj-2ph7, GO-2026-6855, UBUNTU-CVE-2026-97036

## What is CVE-2026-97036?

CVE-2026-97036 is a vulnerability in cmd/go, published on 11 Nov 2026. 

### Official description

On Darwin, building a malicious package that uses cgo could cause arbitrary code execution when using the Apple linker due to passing "-l to_library <path>" in a "#cgo LDFLAGS" directive. The Apple linker recombines the separated arguments "-l" and "to_library" into "-lto_library", which loads an arbitrary LTO plugin dynamic library at link time. The go command now disallows "-l" followed by "to_library" in "#cgo LDFLAGS", rejects "-lazy_library", "-lazy_framework", "-load_hidden", "-library", and "-library-path", and checks recombined "-l" arguments against disallowed linker flags and patterns.

## Which versions are affected by CVE-2026-97036?

1 open source package ship an affected version, including toolchain.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `toolchain` | Go | All versions | 1.26.11, 1.27.4 |

## How do I fix CVE-2026-97036?

Upgrade toolchain to a fixed version for your release line: 1.26.11 or 1.27.4.

## Is CVE-2026-97036 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97036 and fix it if it is affected.

What it is: CVE-2026-97036 is a vulnerability in cmd/go, published on 11 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-97036 in the wild and no public exploit code.

Affected packages and fixed versions:
- toolchain (Go): affected all versions; fixed in 1.26.11, 1.27.4

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-2026-97036/ (Markdown: https://insights.sbomify.com/CVE-2026-97036/index.md)
```

## Sources

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

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