fix: upgrade Go to 1.26.0 to resolve CVE-2025-68121#8884
fix: upgrade Go to 1.26.0 to resolve CVE-2025-68121#8884WSandboxedOCCodeBot wants to merge 1 commit intoknative:mainfrom
Conversation
|
|
Hi @WSandboxedOCCodeBot. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: WSandboxedOCCodeBot The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Summary
Upgrade Go toolchain from 1.24.x to 1.26.0 to resolve a CRITICAL severity Go standard library CVE identified by Trivy container image scanning.
Motivation
Routine security scanning of Knative Eventing container images using Trivy revealed a Go stdlib vulnerability that is resolved in Go 1.26.0. This is a minimal Go toolchain version bump with no functional modifications to the Knative Eventing application code.
Trivy Scan Command
Findings (Before Fix -- Go 1.24.x)
Findings (After Fix -- Go 1.26.0)
CVE Details
crypto/tlsrelated to session resumption that can lead to denial of service. Knative Eventing manages event-driven architectures and uses TLS for broker communication, channel subscriptions, and Kubernetes API access, making this vulnerability directly relevant.Changes
Testing