Go· ()

This monthVendor security release

Go security releases: 1.26.4, 1.25.11

What
Go published security fixes. Upgrade to 1.26.4 / 1.25.11 (whichever matches your branch). Fixes 3 CVEs. Security fixes to the crypto/x509 , mime , and net/textproto packages.
Fix
Upgrade to 1.26.41.25.11
Why this tier
Vendor security release for server software (most severe: CVE-2026-42504).
Exploited
Not known to be exploited · highest EPSS 0.6%
Share this

What to do now#

  1. Check whether you run an affected Go version:
    go version
  2. Upgrade to the fixed release for your branch: 1.26.4, 1.25.11.Vendor announcement
  3. Rebuild and redeploy every Go binary with the fixed toolchain: Go links the standard library into binaries, so upgrading Go on a host does not patch what is already built.
  4. Using distro packages? Distros backport fixes under their own version numbers. Check your distro's status for CVE-2026-27145 (and the other 2 CVEs):Debian · Ubuntu · Red Hat · Alpine

CVEs 3#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-42504Routine7.5 (v3.1)0.6%Nonone
CVE-2026-27145Routine6.5 (v3.1)0.6%Nonone
CVE-2026-42507Routine5.3 (v3.1)0.4%Nonone

Sources#

Built from Go: Go release history + Go: Go vulnerability database (vuln.go.dev), checked . Tier from the published rubric.

Also on today's list

See today's list → · Coming up →

Something wrong on this page?
Anonymous. Reports are checked against the primary source.