The "go bug" command writes to two files with predictable names in the system temporary directory (for example, "/tmp"). An attacker with access to the temporary directory can create a symlink in one of these names, causing "go bug" to overwrite the target of the symlink.
CVE-2026-39819
Score 5.3 from GitHub Security Advisory published 2026-05-07. NVD baseline CVSS 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 24(Track)EG Risk 24/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
May 7, 2026
Last Modified
May 13, 2026
Advisory Details (4)
Auto-updated Jun 17, 2026cmd/go: go bug uses predictable temporary filenames · Issue #78584 · golang/go · GitHub
https://go.dev/issue/78584Vendor Advisories for CVE-2026-39819(8)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:57649Red Hat Product SecurityHigh
Red Hat Security Advisory: golang security update
- RHSA-2026:57194Red Hat Product SecurityHigh
Red Hat Security Advisory: multicluster engine for Kubernetes v2.11.5 security update
- RHSA-2026:49712Red Hat Product SecurityHigh
Red Hat Security Advisory: golang security update
- RHSA-2026:49702Red Hat Product SecurityHigh
Red Hat Security Advisory: golang security update
- RHSA-2026:22112Red Hat Product SecurityHigh
Red Hat Security Advisory: go-toolset:rhel8 security update
- RHSA-2026:22121Red Hat Product SecurityHigh
Red Hat Security Advisory: golang security update
- RHSA-2026:22120Red Hat Product SecurityHigh
Red Hat Security Advisory: golang security update
- CVE-2026-39819Microsoft Security Response Center (MSRC)Medium
Invoking "go bug" follows symlinks in predictable temporary filenames in cmd/go
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | multicluster-engine/hypershift-addon-rhel9-operator:1786912006 | 2026-08-19 | redhat |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-1.25 | 1.25.0-1 ... 1.25.9-1 (11 versions) | 1.25.10-1 | — |
| golang-1.26 | 1.26.0-1 ... 1.26~rc3-2 (9 versions) | 1.26.3-1 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-1.15 | 1.15.15-1 ... 1.15.9-6 (10 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-1.19 | 1.19.10-1 ... 1.19.9-1 (12 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-1.24 | 1.24.12-1 ... 1.24.9-1 (10 versions) | — | — |
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| toolchain | — | 1.26.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 52× 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 165 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-23 19:33 UTCEG score recompute
- 2026-08-23 19:33 UTCVendor advisory
- 2026-08-23 19:33 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 12:43 UTCEG score recompute
- 2026-08-17 12:43 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:42 UTCEG score recompute
- 2026-08-16 04:42 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 03:18 UTCEG score recompute
- 2026-08-14 03:18 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 16:52 UTCEG score recompute
- 2026-08-12 16:52 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 03:28 UTCEG score recompute
- 2026-08-11 03:28 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-10 03:03 UTCEG score recompute
- 2026-08-10 03:03 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 02:38 UTCEG score recompute
- 2026-08-09 02:38 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 02:13 UTCEG score recompute
- 2026-08-08 02:13 UTCGHSA enrichment
- 2026-08-07 01:48 UTCEG score recompute
- 2026-08-07 01:48 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 22:13 UTCEG score recompute
- 2026-08-05 22:13 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 05:29 UTCEG score recompute
- 2026-08-04 05:29 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 04:56 UTCGHSA enrichment
- 2026-08-02 04:30 UTCEG score recompute
- 2026-08-02 04:30 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:10 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 09:53 UTCOSV refresh
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 09:09 UTCGHSA enrichment
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 22:13 UTCGHSA enrichment
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-39819?
When was CVE-2026-39819 disclosed?
Is CVE-2026-39819 actively exploited?
What is the CVSS score of CVE-2026-39819?
How do I remediate CVE-2026-39819?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39819
Is Your Infrastructure Affected by CVE-2026-39819?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.