Answer in brief
CVE-2026-39817 records a Unknown severity vulnerability in Invoking "go tool pack" does not sanitize output paths in cmd/go. The current sources do not mark it as known exploited. The current feed maps toolchain (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps toolchain (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| toolchaingo | >=0 <1.25.10 >=1.26.0-0 <1.26.3 | 1.25.10, 1.26.3 |
Published upstream
May 7, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Aug 26, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Aug 26, 2026
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 source text, attributed separately from HOL analysis.