Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-39819: The "go bug" command writes to two files with predictable names in the system temporary directory (for example

20
Routine
MEDIUM 5.3UPGRADE

CVE-2026-39819 is a medium-severity flaw (CVSS 5.3) affecting go. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorLocal
Attack complexityHigh
Privileges neededLow
User interactionNone
EPSS exploit chance0.2% (top 93%)
CISA exploited listNo
WeaknessCWE-59
Published2026-05-07
Last modified2026-06-17
Publisher (CNA): Go Project · Vendor: golang

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

golang go UPGRADE
Affected: < 1.25.10 · >= 1.26.0 and < 1.26.3
Fixed in: 1.25.10, 1.26.3
Safe to downgrade to: a release before 1.26.0
1. Check installed version
apt-cache policy go || rpm -q go || go --version
2. UPGRADE to 1.25.10 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade go
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade go
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.26.0 (Debian / Ubuntu)
apt-cache madison go sudo apt install go=<VERSION_BEFORE_1.26.0> sudo apt-mark hold go
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list go sudo dnf downgrade go-<VERSION_BEFORE_1.26.0> sudo dnf versionlock add go
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-39819?

go: upgrade to 1.25.10, 1.26.3. Exact commands for each OS are on this page.

Is CVE-2026-39819 being exploited?

CVE-2026-39819 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-39819 affect?

CVE-2026-39819 affects go. Severity is medium (CVSS 5.3). 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 over

How urgent is CVE-2026-39819?

Priority 20/100. No elevated risk signals yet.

Software pages

Go (Golang) vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.