fix(security/UNKNOWN/collector): Update module golang.org/x/mod to v0.40.0 [SECURITY] - #6887
Open
renovate-sh-app[bot] wants to merge 1 commit into
Open
fix(security/UNKNOWN/collector): Update module golang.org/x/mod to v0.40.0 [SECURITY]#6887renovate-sh-app[bot] wants to merge 1 commit into
renovate-sh-app[bot] wants to merge 1 commit into
Conversation
….40.0 [SECURITY] | datasource | package | from | to | | ---------- | ---------------- | ------- | ------- | | go | golang.org/x/mod | v0.38.0 | v0.40.0 | Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
Contributor
Author
ℹ️ Artifact update noticeFile name: collector/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
Contributor
🔍 Dependency ReviewBelow is a review of each Go module dependency that changed in this PR. Each section includes a determination, summary, and links to the relevant release notes/changes between the two versions. golang.org/x/crypto v0.54.0 -> v0.55.0 — ✅ Safe
golang.org/x/mod v0.38.0 -> v0.40.0 — ✅ Safe
golang.org/x/net v0.57.0 -> v0.58.0 — ✅ Safe
golang.org/x/telemetry v0.0.0-20260708182218-49f421fb7959 -> v0.0.0-20260811182544-a038080d80e5 — ✅ Safe
golang.org/x/text v0.40.0 -> v0.41.0 — ✅ Safe
golang.org/x/tools v0.48.0 -> v0.49.0 — ✅ Safe
Notes
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.38.0→v0.40.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog
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
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.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.