[BugFix][CVE] update pprof prebuilt to release/20260610 built with Go 1.25.11 (backport #74669)#74718
Open
mergify[bot] wants to merge 1 commit into
Open
[BugFix][CVE] update pprof prebuilt to release/20260610 built with Go 1.25.11 (backport #74669)#74718mergify[bot] wants to merge 1 commit into
mergify[bot] wants to merge 1 commit into
Conversation
23 tasks
kevincai
approved these changes
Jun 12, 2026
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.
The pprof prebuilt binaries from release/20260520 were built with Go 1.24.10, whose standard library is affected by CVEs fixed in later Go releases, notably CVE-2025-61727 and CVE-2025-61729 (crypto/x509, fixed in Go 1.24.11 / 1.25.5) and subsequent stdlib security fixes.
The release/20260610 binaries are rebuilt with Go 1.25.11, which includes all of those fixes.
Changes:
Both assets were downloaded and their SHA256 digests verified against the GitHub release asset digests; MD5 sums computed from the verified binaries.
Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #74669 done by [Mergify](https://mergify.com).