Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog
cve-program · CVE-2026-56865
PublishedA 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
Read the publisher's advisoryeuvd · EUVD-2026-58513
PublishedA 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
Read the publisher's advisorynvd · CVE-2026-56865
PublishedA 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
Read the publisher's advisoryosv · GO-2026-6179
PublishedA 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
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-56865 · CVE overview and exploitation status
cve-program · CVE-2026-56865
- https://go.dev/issue/80744
- https://groups.google.com/g/golang-announce/c/94pEornpRlI
- https://go.dev/cl/814960
- https://go.dev/cl/815020
- https://pkg.go.dev/vuln/GO-2026-6179
euvd · EUVD-2026-58513
- https://go.dev/issue/80744
- https://groups.google.com/g/golang-announce/c/94pEornpRlI
- https://go.dev/cl/814960
- https://go.dev/cl/815020
- https://pkg.go.dev/vuln/GO-2026-6179
nvd · CVE-2026-56865
- https://go.dev/cl/814960
- https://go.dev/cl/815020
- https://go.dev/issue/80744
- https://groups.google.com/g/golang-announce/c/94pEornpRlI
- https://pkg.go.dev/vuln/GO-2026-6179
osv · GO-2026-6179
Related changes
Linked by CVE identifier- 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 ma… · Advisory content revised · 15 Nov 2026
- 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 ma… · Advisory content revised · 9 Nov 2026