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
CVE-2026-56865
This high-severity CVE scores 8.4 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.4
- EG Score
- 8.4(medium)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity84% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 14, 2026
Advisory Details (5)
Auto-updated Aug 14, 2026x/mod/sumdb/tlog: fix transparency log tile verification bypass · Issue #80744 · golang/go · GitHub
https://go.dev/issue/80744Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 26× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 23:18 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 22:46 UTCEG score recompute
- 2026-08-24 10:31 UTCEG score recompute
- 2026-08-23 09:59 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 08:58 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 20:12 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 19:38 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 19:07 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 17:37 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 05:17 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 04:47 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 15:39 UTCEG score recompute▲ 8.40
- 2026-08-14 15:38 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
- 2026-08-13 22:25 UTCNVD update
- 2026-08-13 22:09 UTCEG score recompute
Show 1 moreShow fewer
- 2026-08-13 22:09 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-347
Frequently asked(5)
What is CVE-2026-56865?
When was CVE-2026-56865 disclosed?
Is CVE-2026-56865 actively exploited?
What is the CVSS score of CVE-2026-56865?
How do I remediate CVE-2026-56865?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56865
Is Your Infrastructure Affected by CVE-2026-56865?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.