Go toolchain · Go · published 2026-05-07

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

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-39817 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 6% of all CVEs. This Go vulnerability: CVSS 5.9 (v3.1). Fixed upstream in Go 1.26.3, 1.25.10. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Go 1.26.3, 1.25.10.

Patch events

  1. This monthSecurity release

    Language runtimeGo

    Go security releases: 1.26.3, 1.25.10

    Upgrade to 1.26.31.25.10

    Why: Vendor security release for server software (most severe: CVE-2026-33811).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (7th pct)FIRST EPSS v2026.06.15
CVSS base score5.9 (v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →