14 Nov 2026 13:57:00 UTC
Invoking "go tool pack" does not sanitize output paths in cmd/go
osv · GO-2026-4979 · Published
CVE-2026-39817
Invoking "go tool pack" does not sanitize output paths in cmd/go
cve-program · severity unknownEUVD CVSS 3.1 5.9 CVSS 3.1 · [email protected] · Primary 5.9 MEDIUMCVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 5.9 MEDIUMosv · severity unknownFixed by toolchain 1.25.10Fixed by toolchain 1.26.3KEV status unknown
cve-program · CVE-2026-39817
PublishedThe "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.
Read the publisher's advisoryeuvd · EUVD-2026-28421
PublishedThe "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.
Read the publisher's advisorynvd · CVE-2026-39817
PublishedThe "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.
Read the publisher's advisoryosv · GO-2026-4979
PublishedThe "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.
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
Risk history
Compare earlier KEV listings and daily EPSS scores. Advisory wording and affected versions have a separate history.
When does an EPSS score appear as a change?
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Other daily score changes remain in this history.
Advisory history
14 saved versionsSee how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
How advisory history works
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
14 Nov 2026 08:00:13 UTC
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 loc…
euvd · EUVD-2026-28421 · Published
12 Nov 2026 15:18:43 UTC
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 loc…
nvd · CVE-2026-39817 · Published
11 Nov 2026 09:34:34 UTC
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 loc…
euvd · EUVD-2026-28421 · Published
9 Nov 2026 09:12:38 UTC
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 loc…
euvd · EUVD-2026-28421 · Published
7 Nov 2026 08:34:43 UTC
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 loc…
euvd · EUVD-2026-28421 · Published
5 Nov 2026 08:02:37 UTC
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 loc…
euvd · EUVD-2026-28421 · Published
3 Nov 2026 07:07:55 UTC
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 loc…
euvd · EUVD-2026-28421 · Published
1 Nov 2026 06:13:51 UTC
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 loc…
euvd · EUVD-2026-28421 · Published
30 Oct 2026 05:58:03 UTC
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 loc…
euvd · EUVD-2026-28421 · Published
28 Oct 2026 04:59:30 UTC
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 loc…
euvd · EUVD-2026-28421 · Published
25 Oct 2026 09:17:18 UTC
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 loc…
nvd · CVE-2026-39817 · Published
24 Oct 2026 13:19:41 UTC
Invoking "go tool pack" does not sanitize output paths in cmd/go
osv · GO-2026-4979 · Published
23 Oct 2026 15:48:27 UTC
Invoking "go tool pack" does not sanitize output paths in cmd/go
cve-program · CVE-2026-39817 · Published