# CVE-2026-97038: Arbitrary code execution via crafted .syso files and cgo linker input files 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:** ALPINE-CVE-2026-97038, DEBIAN-CVE-2026-97038, GHSA-q9p5-q4jx-v656, GO-2026-6853, UBUNTU-CVE-2026-97038

## What is CVE-2026-97038?

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

### Official description

Building a malicious package containing ".syso" files or cgo linker inputs could inject arbitrary linker flags or execute arbitrary code at link time. Linker input files—including ".syso" files, direct object or library inputs in "#cgo LDFLAGS", and libraries in "-L" directories—were passed to the external linker without validating their format or checking for embedded linker options. Across platforms, this allowed executing GNU ld implicit linker scripts disguised as libraries or ".syso" files (or loaded via "-l:<filename>" or "-l" containing path separators), injecting unallowlisted linker flags via PE/COFF ".drectve" sections on Windows or Mach-O "LC_LINKER_OPTION" load commands on Darwin, or invoking LTO plugins via GCC or LLVM LTO intermediate representation sections in ELF, PE/COFF, or Mach-O objects. The go command now verifies that ".syso" files, direct linker inputs, and libraries in "-L" directories are valid binary objects or archives that do not contain unallowlisted ".drectve" directives, "LC_LINKER_OPTION" load commands, or LTO IR sections, and disallows "-l:<filename>" and ":", "=", or path separators in "-l" flags.

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

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-97038?

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

## Is CVE-2026-97038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97038 is a vulnerability in cmd/go, published on 11 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-97038 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-97038/ (Markdown: https://insights.sbomify.com/CVE-2026-97038/index.md)
```

## Sources

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

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