fix: upgrade Go to 1.25.5 to address CVE-2025-61729

[Harishma-Hari]

What type of PR is this?

kind bug

What this PR does / why we need it:

This PR upgrades the Go version from 1.24.2 to 1.25.5 to address CVE-2025-61729, a high-severity security vulnerability in the crypto/x509 package.

The vulnerability (CVSS Score: 7.5) causes excessive resource consumption through quadratic runtime in HostnameError.Error() when constructing error strings. A malicious actor could provide a certificate that results in unlimited host printing, leading to denial of service through resource exhaustion.

Which issue(s) this PR fixes:

Fixes CVE-2025-61729

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Upgraded Go to version 1.25.5 to fix CVE-2025-61729, a high-severity security vulnerability in crypto/x509 that could lead to 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 saad-ali 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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Harishma-Hari / name: Harishma Hari (40b2af3)

[k8s-ci-robot]

Welcome @Harishma-Hari!

It looks like this is your first PR to kubernetes-csi/external-provisioner 🎉. 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/external-provisioner 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]

Go version used in this project is defined in csi-release-tools repository, https://github.com/kubernetes-csi/csi-release-tools/blob/707a99ecae026a8faa36d60aa9ea88505b5865df/prow.sh#L89

"Someone" needs to sync it into the external-provisioner repo via git subtree, as described here.

And please review and edit AI generated output - the PR description is huge and full of useless information. This would be enough:

This PR upgrades the Go version from 1.24.2 to 1.25.5 to address GHSA-7c64-f9jr-v9h2, a high-severity security vulnerability in the crypto/x509 package.

[jsafrane]

/close
this was already done as part of #1467

[k8s-ci-robot]

@jsafrane: Closed this PR.

Details

In response to this:

/close
this was already done as part of #1467

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.