CVE-2026-39817

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2026-05-07. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 7, 2026

Last Modified

May 13, 2026

Advisory Details (4)

Auto-updated Jun 14, 2026
No patch confirmed yet.
generic

GO-2026-4979 - Go Packages

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

cmd/go: go tool pack does not sanitize output paths · Issue #78778 · golang/go · GitHub

https://go.dev/issue/78778
generic
https://go.dev/cl/767520

Vendor Advisories for CVE-2026-39817(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17869120062026-08-19redhat
redhatoadp/oadp-velero-rhel9:17840588222026-07-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 5 ecosystems)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
golang-1.251.25.0-1 ... 1.25.9-1 (11 versions)1.25.10-1—
golang-1.261.26.0-1 ... 1.26~rc3-2 (9 versions)1.26.3-1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)——
Go(1)
PackageVulnerable rangeFixed inDependents
toolchain—1.26.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 73× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 185 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-23 19:33 UTCEG score recompute
  3. 2026-08-23 19:33 UTCVendor advisory
  4. 2026-08-23 19:33 UTCGHSA enrichment
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 12:43 UTCEG score recompute
  12. 2026-08-17 12:43 UTCVendor advisory
  13. 2026-08-17 12:43 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 04:43 UTCEG score recompute
  16. 2026-08-16 04:43 UTCVendor advisory
  17. 2026-08-16 04:43 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 02:25 UTCEG score recompute
  20. 2026-08-15 02:25 UTCVendor advisory
  21. 2026-08-15 02:25 UTCGHSA enrichment
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 03:18 UTCEG score recompute
  24. 2026-08-14 03:18 UTCVendor advisory
  25. 2026-08-14 03:18 UTCGHSA enrichment
Show 75 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-12 23:40 UTCEG score recompute
  3. 2026-08-12 23:40 UTCVendor advisory
  4. 2026-08-12 23:40 UTCGHSA enrichment
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-12 00:33 UTCEG score recompute
  7. 2026-08-12 00:33 UTCVendor advisory
  8. 2026-08-12 00:33 UTCGHSA enrichment
  9. 2026-08-11 13:43 UTCEPSS rescore
  10. 2026-08-11 01:24 UTCEG score recompute
  11. 2026-08-11 01:24 UTCVendor advisory
  12. 2026-08-11 01:24 UTCGHSA enrichment
  13. 2026-08-11 00:00 UTCEPSS rescore
  14. 2026-08-10 01:36 UTCEG score recompute
  15. 2026-08-10 01:36 UTCVendor advisory
  16. 2026-08-10 01:36 UTCGHSA enrichment
  17. 2026-08-09 13:46 UTCEPSS rescore
  18. 2026-08-09 02:29 UTCEG score recompute
  19. 2026-08-09 02:29 UTCVendor advisory
  20. 2026-08-09 02:29 UTCGHSA enrichment
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-07 20:29 UTCEG score recompute
  23. 2026-08-07 20:29 UTCVendor advisory
  24. 2026-08-07 20:29 UTCGHSA enrichment
  25. 2026-08-06 21:21 UTCEG score recompute
  26. 2026-08-06 21:21 UTCVendor advisory
  27. 2026-08-06 21:21 UTCGHSA enrichment
  28. 2026-08-06 13:46 UTCEPSS rescore
  29. 2026-08-05 22:13 UTCEG score recompute
  30. 2026-08-05 22:13 UTCVendor advisory
  31. 2026-08-05 22:13 UTCGHSA enrichment
  32. 2026-08-05 19:17 UTCEPSS rescore
  33. 2026-08-04 15:10 UTCEPSS rescore
  34. 2026-08-04 10:38 UTCEPSS rescore
  35. 2026-08-04 03:16 UTCEG score recompute
  36. 2026-08-04 03:16 UTCVendor advisory
  37. 2026-08-04 03:16 UTCGHSA enrichment
  38. 2026-08-03 10:36 UTCEPSS rescore
  39. 2026-08-03 03:44 UTCVendor advisory
  40. 2026-08-03 03:44 UTCGHSA enrichment
  41. 2026-08-02 04:30 UTCEG score recompute
  42. 2026-08-02 04:30 UTCVendor advisory
  43. 2026-08-02 04:30 UTCGHSA enrichment
  44. 2026-08-02 02:27 UTCEPSS rescore
  45. 2026-08-01 04:16 UTCEPSS rescore
  46. 2026-07-30 16:28 UTCEPSS rescore
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-27 14:13 UTCEPSS rescore
  49. 2026-07-26 14:54 UTCEPSS rescore
  50. 2026-07-26 14:54 UTCEPSS rescore
  51. 2026-07-25 14:18 UTCEPSS rescore
  52. 2026-07-25 14:18 UTCEPSS rescore
  53. 2026-07-24 14:17 UTCEPSS rescore
  54. 2026-07-24 14:17 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 14:18 UTCEPSS rescore
  57. 2026-07-23 03:10 UTCEG score recompute
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-21 15:24 UTCEPSS rescore
  60. 2026-07-20 17:08 UTCEPSS rescore
  61. 2026-07-19 14:31 UTCEPSS rescore
  62. 2026-07-18 10:04 UTCEPSS rescore
  63. 2026-07-16 17:03 UTCEPSS rescore
  64. 2026-07-16 09:53 UTCOSV refresh
  65. 2026-07-15 16:57 UTCEPSS rescore
  66. 2026-07-15 16:57 UTCEPSS rescore
  67. 2026-07-15 02:00 UTCEPSS rescore
  68. 2026-07-13 22:30 UTCEPSS rescore
  69. 2026-07-13 06:13 UTCEPSS rescore
  70. 2026-07-13 06:13 UTCEPSS rescore
  71. 2026-07-11 08:27 UTCEPSS rescore
  72. 2026-07-09 19:10 UTCEPSS rescore
  73. 2026-07-08 15:15 UTCEPSS rescore
  74. 2026-07-07 13:46 UTCEPSS rescore
  75. 2026-07-06 16:27 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-39817?
CVE-2026-39817 is a medium vulnerability published on May 7, 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.
When was CVE-2026-39817 disclosed?
CVE-2026-39817 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39817 actively exploited?
CVE-2026-39817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.6% of all scored CVEs.
What is the CVSS score of CVE-2026-39817?
CVE-2026-39817 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-39817?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39817, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39817

Explore →

Is Your Infrastructure Affected by CVE-2026-39817?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs