Go toolchain · Go · published 2026-08-13

CVE-2026-56865Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog

Routine No exploitation evidence; EPSS 0.1%.

CVE-2026-56865 is not known to be exploited in the wild. EPSS estimates a 0.1% chance of exploitation in the next 30 days, higher than 2% of all CVEs. This Go vulnerability: CVSS 8.4 (v3.1), a successful attack gives total control of the component. Fixed upstream in Go 1.26.6, 1.25.13. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Go 1.26.6, 1.25.13.

Patch events

  1. This monthSecurity release

    Language runtimeGo

    Go security releases: 1.26.6, 1.25.13

    Upgrade to 1.26.61.25.13

    Why: CVE-2026-39821: EPSS 1.8% with high severity (CVSS 9.6).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.1% (3th pct)FIRST EPSS v2026.06.15
CVSS base score8.4 (v3.1)
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

A malicious GOPROXY was previously capable of forging up to two sumdb tiles that allow for a requested module to bypass the GOSUMDB check and persist attacker-controlled module content to a local Go module cache. This attack allows for a malicious GOPROXY to serve malicious module content that cannot be detected by evaluating the transparency log. All tiles are now correctly verified against their parents. In order to determine if you have been affected: rm -r go.sum go.work.sum vendor/ && go mod tidy

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

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

Also on today's list

See today's list → · Coming up →