Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog

cve-program · severity unknownEUVD CVSS 3.1 8.4 CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 8.4 HIGHosv · severity unknownFixed by toolchain 1.25.13Fixed by toolchain 1.26.6Fixed by toolchain 1.27.0-rc.3Fixed by golang.org/x/mod 0.40.0KEV status unknown

cve-program · CVE-2026-56865

Published

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

Read the publisher's advisory

euvd · EUVD-2026-58513

Published

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

Read the publisher's advisory

nvd · CVE-2026-56865

Published

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

Read the publisher's advisory

osv · GO-2026-6179

Published

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

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-56865

Published

Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog

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

Source published
13 Aug 2026 21:58:53 UTC
Source modified
14 Aug 2026 15:34:17 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

euvd · EUVD-2026-58513

Published

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…

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

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 13, 2026, 9:58:53 PM

dateUpdated: Aug 14, 2026, 3:34:17 PM

23 related source bulletins · separate from aliases

RHSA-2026:96629: Red Hat Security Advisory: Red Hat multicluster engine for Kubernetes - 2.17.4

CVE-2026-25681 · CVE-2026-27136 · CVE-2026-33818 · CVE-2026-39821 · CVE-2026-39822 · CVE-2026-39834 · CVE-2026-41178 · CVE-2026-42502 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865 · CVE-2026-63209 · CVE-2026-84292 · CVE-2026-84304 · CVE-2026-84375 · CVE-2026-84394 · CVE-2026-84445 · CVE-2026-88031 · CVE-2026-93748 · CVE-2026-106445 · CVE-2026-106446

SUSE-SU-2026:24282-1: Security update for helm

CVE-2026-33814 · CVE-2026-35204 · CVE-2026-35205 · CVE-2026-35206 · CVE-2026-41178 · CVE-2026-41888 · CVE-2026-48978 · CVE-2026-50151 · CVE-2026-50163 · CVE-2026-56852 · CVE-2026-56854 · CVE-2026-56855 · CVE-2026-56864 · CVE-2026-56865 · CVE-2026-63209 · CVE-2026-78662 · CVE-2026-81870 · CVE-2026-81871 · CVE-2026-81872 · CVE-2026-85732

SUSE-SU-2026:23301-1: Security update for go1.26

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

openSUSE-SU-2026:21592-1: Security update for go1.25

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

WID-SEC-W-2026-2850: Golang Go: Mehrere Schwachstellen

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-46600 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

openSUSE-SU-2026:21983-1: Security update for helm

CVE-2026-33814 · CVE-2026-35204 · CVE-2026-35205 · CVE-2026-35206 · CVE-2026-41178 · CVE-2026-41888 · CVE-2026-48978 · CVE-2026-50151 · CVE-2026-50163 · CVE-2026-56852 · CVE-2026-56854 · CVE-2026-56855 · CVE-2026-56864 · CVE-2026-56865 · CVE-2026-78662 · CVE-2026-81871 · CVE-2026-81872 · CVE-2026-85732

RHSA-2026:74609: Red Hat Security Advisory: Cluster Observability Operator 1.5.3

CVE-2026-19534 · CVE-2026-39244 · CVE-2026-41178 · CVE-2026-42504 · CVE-2026-45623 · CVE-2026-56864 · CVE-2026-56865 · CVE-2026-59887 · CVE-2026-63199 · CVE-2026-71556 · CVE-2026-73086 · CVE-2026-75899 · CVE-2026-75931 · CVE-2026-75975 · CVE-2026-76172 · CVE-2026-84292 · CVE-2026-84394 · CVE-2026-84445 · CVE-2026-84961 · CVE-2026-92000 · CVE-2026-100690

SUSE-SU-2026:23576-1: Security update for go1.26-openssl

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

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

CVE-2026-56865

RHSA-2026:99960: Red Hat Security Advisory: multicluster engine for Kubernetes v2.10.8 security update

CVE-2026-25681 · CVE-2026-27136 · CVE-2026-39821 · CVE-2026-39822 · CVE-2026-39834 · CVE-2026-41178 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865 · CVE-2026-63209 · CVE-2026-84304 · CVE-2026-93748 · CVE-2026-106445 · CVE-2026-106446

SUSE-SU-2026:23300-1: Security update for go1.25

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

openSUSE-SU-2026:21696-1: Security update for go1.25-openssl

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

openSUSE-SU-2026:21593-1: Security update for go1.26

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

openSUSE-SU-2026:11516-1: go1.25-1.25.13-1.1 on GA media

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

openSUSE-SU-2026:11536-1: go1.27-1.27rc3-1.1 on GA media

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

RHSA-2026:67714: Red Hat Security Advisory: RHACS 4.11.4 security and bug fix update

CVE-2026-33818 · CVE-2026-46600 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-75838 · CVE-2026-82417 · CVE-2026-84375

SUSE-SU-2026:23573-1: Security update for go1.25-openssl

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

SUSE-SU-2026:23973-1: Security update for helm

CVE-2026-33814 · CVE-2026-35204 · CVE-2026-35205 · CVE-2026-35206 · CVE-2026-41178 · CVE-2026-41888 · CVE-2026-48978 · CVE-2026-50151 · CVE-2026-50163 · CVE-2026-56852 · CVE-2026-56854 · CVE-2026-56855 · CVE-2026-56864 · CVE-2026-56865 · CVE-2026-78662 · CVE-2026-81871 · CVE-2026-81872 · CVE-2026-85732

openSUSE-SU-2026:11517-1: go1.26-1.26.6-1.1 on GA media

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

openSUSE-SU-2026:11575-1: helm-4.2.4-1.1 on GA media

CVE-2026-50163 · CVE-2026-56864 · CVE-2026-56865

openSUSE-SU-2026:21705-1: Security update for go1.26-openssl

CVE-2026-33818 · CVE-2026-39821 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865

RHSA-2026:99958: Red Hat Security Advisory: multicluster engine for Kubernetes v2.9.9 security update

CVE-2026-25681 · CVE-2026-27136 · CVE-2026-39821 · CVE-2026-39822 · CVE-2026-39834 · CVE-2026-41178 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-56864 · CVE-2026-56865 · CVE-2026-63209 · CVE-2026-84304 · CVE-2026-93748 · CVE-2026-106445 · CVE-2026-106446 · CVE-2026-116591

SUSE-SU-2026:23984-1: Security update for helm

CVE-2026-33814 · CVE-2026-35204 · CVE-2026-35205 · CVE-2026-35206 · CVE-2026-41178 · CVE-2026-41888 · CVE-2026-48978 · CVE-2026-50151 · CVE-2026-50163 · CVE-2026-56852 · CVE-2026-56854 · CVE-2026-56855 · CVE-2026-56864 · CVE-2026-56865 · CVE-2026-78662 · CVE-2026-81871 · CVE-2026-81872 · CVE-2026-85732

Source published
Aug 13, 2026, 9:58:53 PM (timezone not stated)
Source modified
Aug 14, 2026, 3:34:17 PM (timezone not stated)
Saved here
17 Nov 2026 16:37:37 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd · CVE-2026-56865

Published

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…

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

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Awaiting Analysis

Weakness classifications: CWE-347

Original publisher date fields

published: 2026-08-13T22:17:22.797

lastModified: 2026-09-03T16:37:52.170

Source published
13 Aug 2026 22:17:22 UTC
Source modified
3 Sep 2026 16:37:52 UTC
Saved here
25 Oct 2026 14:19:10 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary · 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

osv · GO-2026-6179

Published

Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog

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

Source published
13 Aug 2026 21:43:54 UTC
Source modified
19 Aug 2026 12:25:40 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 17:49 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current