test: fix CVE-2025-47912 error

[andyzhangx]

What type of PR is this?
/kind failing-test

What this PR does / why we need it:
test: fix CVE-2025-47912 error

azurediskplugin (gobinary)
==========================
Total: 10 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 10, CRITICAL: 0)

┌─────────┬────────────────┬──────────┬────────┬───────────────────┬────────────────┬────────────────────────────────────────────────────────────┐
│ Library │ Vulnerability  │ Severity │ Status │ Installed Version │ Fixed Version  │                           Title                            │
├─────────┼────────────────┼──────────┼────────┼───────────────────┼────────────────┼────────────────────────────────────────────────────────────┤
│ stdlib  │ CVE-2025-47912 │ HIGH     │ fixed  │ v1.24.6           │ 1.24.8, 1.25.2 │ [net/url: insufficient validation of bracketed IPv6        │
│         │                │          │        │                   │                │ hostnames]                                                 │
│         │                │          │        │                   │                │ https://avd.aquasec.com/nvd/cve-2025-47912                 │

📣 Notices:
  - Version 0.67.2 of Trivy is now available, current version is 0.65.0

To suppress version checks, run Trivy scans with the --skip-version-check flag

│         ├────────────────┤          │        │                   │                ├────────────────────────────────────────────────────────────┤
│         │ CVE-2025-58183 │          │        │                   │                │ [archive/tar: unbounded allocation when parsing GNU sparse │
│         │                │          │        │                   │                │ map]                                                       │
│         │                │          │        │                   │                │ https://avd.aquasec.com/nvd/cve-2025-58183                 │
│         ├────────────────┤          │        │                   │                ├────────────────────────────────────────────────────────────┤
│         │ CVE-2025-58185 │          │        │                   │                │ [encoding/asn1: pre-allocating memory when parsing DER     │
│         │                │          │        │                   │                │ payload can cause memory exhaustion]                       │
│         │                │          │        │                   │                │ https://avd.aquasec.com/nvd/cve-2025-58185                 │
│         ├────────────────┤          │        │                   │                ├────────────────────────────────────────────────────────────┤
│         │ CVE-2025-58186 │          │        │                   │                │ [net/http: lack of limit when parsing cookies can cause    │
│         │                │          │        │                   │                │ memory exhaustion]                                         │
│         │                │          │        │                   │                │ https://avd.aquasec.com/nvd/cve-2025-58186                 │
│         ├────────────────┤          │        │                   ├────────────────┼────────────────────────────────────────────────────────────┤
│         │ CVE-2025-58187 │          │        │                   │ 1.24.9, 1.25.3 │ [crypto/x509: quadratic complexity when checking name      │
│         │                │          │        │                   │                │ constraints]                                               │
│         │                │          │        │                   │                │ https://avd.aquasec.com/nvd/cve-2025-58187                 │
│         ├────────────────┤          │        │                   ├────────────────┼────────────────────────────────────────────────────────────┤
│         │ CVE-2025-58188 │          │        │                   │ 1.24.8, 1.25.2 │ [crypto/x509: panic when validating certificates with DSA  │
│         │                │          │        │                   │                │ public keys]                                               │
│         │                │          │        │                   │                │ https://avd.aquasec.com/nvd/cve-2025-58188                 │
│         ├────────────────┤          │        │                   │                ├────────────────────────────────────────────────────────────┤
│         │ CVE-2025-58189 │          │        │                   │                │ [crypto/tls: ALPN negotiation errors can contain arbitrary │
│         │                │          │        │                   │                │ text]                                                      │
│         │                │          │        │                   │                │ https://avd.aquasec.com/nvd/cve-2025-58189                 │
│         ├────────────────┤          │        │                   │                ├────────────────────────────────────────────────────────────┤
│         │ CVE-2025-61723 │          │        │                   │                │ [encoding/pem: quadratic complexity when parsing some      │
│         │                │          │        │                   │                │ invalid inputs]                                            │
│         │                │          │        │                   │                │ https://avd.aquasec.com/nvd/cve-2025-61723                 │
│         ├────────────────┤          │        │                   │                ├────────────────────────────────────────────────────────────┤
│         │ CVE-2025-61724 │          │        │                   │                │ [net/textproto: excessive CPU consumption in               │
│         │                │          │        │                   │                │ Reader.ReadResponse]                                       │
│         │                │          │        │                   │                │ https://avd.aquasec.com/nvd/cve-2025-61724                 │
│         ├────────────────┤          │        │                   │                ├────────────────────────────────────────────────────────────┤
│         │ CVE-2025-61725 │          │        │                   │                │ [net/mail: excessive CPU consumption in ParseAddress]      │
│         │                │          │        │                   │                │ https://avd.aquasec.com/nvd/cve-2025-61725                 │
└─────────┴────────────────┴──────────┴────────┴───────────────────┴────────────────┴────────────────────────────────────────────────────────────┘

Which issue(s) this PR fixes:

Fixes #

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Special notes for your reviewer:

Release note:

none

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

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

[andyzhangx]

/cherrypick release-1.27

[andyzhangx]

/cherrypick release-1.26

[andyzhangx]

/cherrypick release-1.25

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #2223

In response to this:

/cherrypick release-1.27

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.

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #2224

In response to this:

/cherrypick release-1.26

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.

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #2225

In response to this:

/cherrypick release-1.25

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.