Fix CVE-2025-61729: Upgrade Go toolchain from 1.24.6 to 1.25.5

[Harishma-Hari]

What type of PR is this?

/kind bug

What this PR does / why we need it:

This PR fixes CVE-2025-61729, a high-severity security vulnerability in Go's crypto/x509 package. The vulnerability causes excessive resource consumption in HostnameError.Error() due to unbounded host printing and quadratic string concatenation, which can be exploited by malicious actors providing specially crafted certificates.

The fix upgrades the Go toolchain from version 1.24.6 (vulnerable) to version 1.25.5 (patched).

Which issue(s) this PR fixes:

Fixes CVE-2025-61729

Special notes for your reviewer:

• This is a security patch that only updates the Go toolchain version
• No code changes required - the fix is in the Go standard library
• Build and tests pass successfully with Go 1.25.5
• CVSS Score: 7.5 (High severity)
• Attack Vector: Network (AV:N)
• No user interaction required (UI:N)

Does this PR introduce a user-facing change?:

Fixed CVE-2025-61729 by upgrading Go toolchain to 1.25.5, addressing a high-severity vulnerability in crypto/x509 that could cause excessive resource consumption.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Harishma-Hari
Once this PR has been reviewed and has the lgtm label, please assign msau42 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @Harishma-Hari!

It looks like this is your first PR to kubernetes-csi/node-driver-registrar 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-csi/node-driver-registrar has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Harishma-Hari. Thanks for your PR.

I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions 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.

[jsafrane]

/close
this was merged as part of #548

[k8s-ci-robot]

@jsafrane: Closed this PR.

Details

In response to this:

/close
this was merged as part of #548

Instructions 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.