cve.bz

CVE-2026-42501 golang go

7.5 highEPSS 0.2%Fix available

High (7.5) in golang go. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in toolchain 1.25.10, 1.26.3.

On this page
A malicious module proxy can exploit a flaw in the go command's validation of module checksums to bypass checksum database validation. This vulnerability affects any user using an untrusted module proxy (GOMODPROXY) or checksum database (GOSUMDB). A malicious module proxy can serve altered versions of the Go toolchain. When selecting a different version of the Go toolchain than the currently installed toolchain (due to the GOTOOLCHAIN environment variable, or a go.work or go.mod with a toolchain line), the go command will download and execute a toolchain provided by the module proxy. A malicious module proxy can bypass checksum database validation for this downloaded toolchain. Since this vulnerability affects the security of toolchain downloads, setting GOTOOLCHAIN to a fixed version is not sufficient. You must upgrade your base Go toolchain. The go tool always validates the hash of a toolchain before executing it, so fixed versions will refuse to execute any cached, altered versions of the toolchain. The go tool trusts go.sum files to contain accurate hashes of the current module's dependencies. A malicious proxy exploiting this vulnerability to serve an altered module will have caused an incorrect hash to be recorded in the go.sum. Users who have configured a non-trusted GOPROXY can determine if they have been affected by running "rm go.sum ; go mod tidy ; go mod verify", which will revalidate all dependencies of the current module. The specific flaw in more detail: The go command consults the checksum database to validate downloaded modules, when a module is not listed in the go.sum file. It verifies that the module hash reported by the checksum database matches the hash of the downloaded module. If, however, the checksum database returns a successful response that contains no entry for the module, the go command incorrectly permitted validation to succeed. A module proxy may mirror or proxy the checksum database, in which case the go command will not connect to the checksum database directly. Checksums reported by the checksum database are cryptographically signed, so a malicious proxy cannot alter the reported checksum for a module. However, a proxy which returns an empty checksum response, or a checksum response for an unrelated module, could cause the go command to proceed as if a downloaded module has been validated.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-05-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-42501 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-42501?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-42501?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-42501 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Go toolchain cmd/gobefore 1.25.10
Go toolchain cmd/gofrom 1.26.0-0 before 1.26.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GO-2026-4984Gotoolchain<1.25.10
>=1.26.0-0 <1.26.3
1.25.10, 1.26.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12golang-1.19no fix listedDEBIAN-CVE-2026-42501
Debian13golang-1.24no fix listedDEBIAN-CVE-2026-42501
Debian14golang-1.261.26.3-1DEBIAN-CVE-2026-42501
Ubuntu14.04:LTSgolang-1.10no fix listedUBUNTU-CVE-2026-42501
Ubuntu16.04:LTSgolang-1.6, golang-1.10no fix listedUBUNTU-CVE-2026-42501
Ubuntu18.04:LTSgolang-1.8, golang-1.9, golang-1.10no fix listedUBUNTU-CVE-2026-42501
Ubuntu20.04:LTSgolang-1.13, golang-1.14, golang-1.18 and 3 moreno fix listedUBUNTU-CVE-2026-42501
Ubuntu22.04:LTSgolang-1.17, golang-1.18, golang-1.20 and 5 moreno fix listedUBUNTU-CVE-2026-42501
Ubuntu24.04:LTSgolang-1.21, golang-1.22, golang-1.23 and 2 moreno fix listedUBUNTU-CVE-2026-42501
Ubuntu25.10, 26.04:LTSgolang-1.23, golang-1.24, golang-1.25no fix listedUBUNTU-CVE-2026-42501
UbuntuPro:16.04:LTSgolang-1.13, golang-1.18no fix listedUBUNTU-CVE-2026-42501
UbuntuPro:18.04:LTSgolang-1.13, golang-1.16, golang-1.18no fix listedUBUNTU-CVE-2026-42501
UbuntuPro:20.04:LTSgolang-1.16no fix listedUBUNTU-CVE-2026-42501
UbuntuPro:22.04:LTSgolang-1.13no fix listedUBUNTU-CVE-2026-42501
Red Hatenterprise_linux:8::appstreamdelve, delve-debuginfo, delve-debugsource0:1.25.2-1.module+el8.10.0+23746+9db33b5eRHSA-2026:22112
Red Hatenterprise_linux:8::appstreamgolang, go-toolset, golang-bin and 5 more0:1.25.10-1.module+el8.10.0+24308+5c4a16b7RHSA-2026:22112
Red Hatenterprise_linux:9::appstreamgolang, go-toolset, golang-bin and 5 more0:1.26.3-1.el9_8RHSA-2026:22121
Red Hatenterprise_linux:10.2golang, go-toolset, golang-bin and 5 more0:1.26.3-4.el10_2RHSA-2026:22120
Red Hathummingbird:1golang-fips1.25, golang-fips1.25-bin, golang-fips1.25-src and 4 more0:1.25.9-0.1.1.hum1RHSA-2026:32987
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0go1.25-openssl1.25.12-160000.1.1SUSE-SU-2026:22638-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0go1.26-openssl1.26.4-160000.1.1SUSE-SU-2026:22572-1
openSUSELeap 16.0go1.25-openssl1.25.12-160000.1.1openSUSE-SU-2026:21319-1
openSUSELeap 16.0go1.26-openssl1.26.4-160000.1.1openSUSE-SU-2026:21254-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSETumbleweedgo1.251.25.10-1.1openSUSE-SU-2026:10723-1
openSUSETumbleweedgo1.261.26.3-1.1openSUSE-SU-2026:10741-1
openSUSETumbleweedopa1.16.2-1.1openSUSE-SU-2026:10755-1
AlmaLinux8delve1.25.2-1.module_el8.10.0+4074+24330916ALSA-2026:22112
AlmaLinux8golang, go-toolset, golang-bin and 5 more1.25.10-1.module_el8.10.0+4187+c45165c4ALSA-2026:22112
AlmaLinux9golang, go-toolset, golang-bin and 5 more1.26.3-1.el9_8ALSA-2026:22121
Rocky Linux8delve0:1.25.2-1.module+el8.10.0+40035+ee0a7047RLSA-2026:22112
Rocky Linux8golang0:1.25.10-1.module+el8.10.0+40200+0fd0f175RLSA-2026:22112
Rocky Linux9golang0:1.26.3-1.el9_8RLSA-2026:22121
Rocky Linux10golang0:1.26.3-4.el10_2RLSA-2026:22120
Alpinev3.23go1.25.10-r0ALPINE-CVE-2026-42501
Alpinev3.24go1.26.3-r0ALPINE-CVE-2026-42501
Alpinev3.24rclone1.74.1-r0ALPINE-CVE-2026-42501
Azure Linux3golangno fix listedAZL-98799
Alpaquita23, 25go1.25.10-r0BELL-CVE-2026-42501
Alpaquitastreamgo1.26.3-r0BELL-CVE-2026-42501
BellSoft Hardened Containers23, 25go1.25.10-r0BELL-CVE-2026-42501
BellSoft Hardened Containersstreamgo1.26.3-r0BELL-CVE-2026-42501

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This Moderate impact flaw in the Go command (`cmd/go`) allows a malicious module proxy to bypass checksum validation, potentially leading to the execution of untrusted Go toolchains. Red Hat products utilizing the Go command are vulnerable if configured to use an untrusted module proxy or checksum database, as this could compromise the integrity of the Go development environment. Exploitation requires user interaction with a compromised proxy.

Red Hat's mitigation

To verify the integrity of Go module dependencies and detect potential tampering by a malicious proxy, users can revalidate all dependencies of the current module. This process involves removing the existing `go.sum` file and then re-generating and verifying module checksums.

Execute the following commands in your module's root directory:

```bash

rm go.sum

go mod tidy

go mod verify

```

This operation will re-download and re-verify all module dependencies. Be aware that this may affect your local module cache and could require re-building projects.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10golang-0:1.26.3-4.el10_2Fixed 2026-06-01RHSA-2026:22120
Red Hat Enterprise Linux 10.0 Extended Update Supportgolang-0:1.26.5-1.el10_0Fixed 2026-08-03RHSA-2026:49702
Red Hat Enterprise Linux 8go-toolset:rhel8-8100020260518131104.a3795deeFixed 2026-06-01RHSA-2026:22112
Red Hat Enterprise Linux 9golang-0:1.26.3-1.el9_8Fixed 2026-06-01RHSA-2026:22121
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutionsgolang-0:1.26.5-1.el9_2Fixed 2026-08-31RHSA-2026:61253
Red Hat Enterprise Linux 9.4 Update Services for SAP Solutionsgolang-0:1.26.5-1.el9_4Fixed 2026-08-20RHSA-2026:57649
Red Hat Enterprise Linux 9.6 Extended Update Supportgolang-0:1.26.5-1.el9_6Fixed 2026-08-03RHSA-2026:49712
Red Hat Hardened Imagesgolang1-25-main-1.25.11-2.hum1Fixed 2026-06-04RHSA-2026:23262
Red Hat Hardened Imagesgolang1-26-main-1.26.4-2.hum1Fixed 2026-06-04RHSA-2026:23264
Red Hat Hardened Imagesgolang-fips1-25-main-1.25.9-0.1.1.hum1Fixed 2026-06-29RHSA-2026:32987
Exploit Intelligenceexploit-intelligence-tech-preview/vulnerability-analysis-rhel9Fix deferred
Multicluster Engine for Kubernetesmulticluster-engine/addon-manager-rhel9Affected
Multicluster Engine for Kubernetesmulticluster-engine/backplane-rhel9-operatorNot affected
Multicluster Engine for Kubernetesmulticluster-engine/clusterlifecycle-state-metrics-rhel9Affected
Multicluster Engine for Kubernetesmulticluster-engine/hypershift-addon-rhel9-operatorAffected
Multicluster Engine for Kubernetesmulticluster-engine/maestro-rhel9Affected
Multicluster Engine for Kubernetesmulticluster-engine/managedcluster-import-controller-rhel9Affected
Multicluster Engine for Kubernetesmulticluster-engine/multicloud-manager-rhel9Affected
Multicluster Engine for Kubernetesmulticluster-engine/placement-rhel9Affected
Multicluster Engine for Kubernetesmulticluster-engine/registration-operator-rhel9Affected
30 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-42501.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON