Repository navigation
chore(deps): update module golang.org/x/mod to v0.40.0 [security] - autoclosed - #70
scality-renovate[bot] wants to merge 1 commit into
Conversation
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
Dependency Bump EvaluationVersion change: golang.org/x/mod v0.38.0 → v0.40.0 (minor, 2 versions) Changes:
Breaking changes: None — no API changes between v0.38.0 and v0.40.0 Security concerns: The CVEs address supply chain integrity of Go module verification (sumdb/tlog). While this project does not directly import the affected packages, they are used by the Go toolchain during module resolution. Fixing these strengthens build-time supply chain security. Priority: merge promptly. Impact on codebase:
Recommendation: SAFE TO MERGE (once CI passes — build, lint, and test checks are currently in progress) Notes: PR authored by scality-renovate[bot] (not dependabot), so providing evaluation as comment only. — Claude Code |
005cc6f to
15a2521
Compare
This PR contains the following updates:
v0.38.0→v0.40.0Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog
BIT-golang-2026-56865 / CVE-2026-56865 / GO-2026-6179
More information
Details
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
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Ignore unrelated, unauthenticated hashes in Lookup in golang.org/x/mod/sumdb
BIT-golang-2026-56864 / CVE-2026-56864 / GO-2026-6180
More information
Details
A malicious GOSUMDB was capable of serving arbitrary module content not contained within the transparency log.
This attack allows for a coordinating GOPROXY and GOSUMDB to serve a client malicious module content that cannot be detected by evaluating the transparency log.
In order to determine if you have been affected:
rm -r go.sum go.work.sum vendor/ && go mod tidy
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.