fix: CVE-2025-5187

[andyzhangx]

What type of PR is this?
/kind bug

What this PR does / why we need it:
fix: CVE-2025-5187

┌───────────────────┬───────────────┬──────────┬────────┬───────────────────┬─────────────────────────┬─────────────────────────────────────────────────────┐
│      Library      │ Vulnerability │ Severity │ Status │ Installed Version │      Fixed Version      │                        Title                        │
├───────────────────┼───────────────┼──────────┼────────┼───────────────────┼─────────────────────────┼─────────────────────────────────────────────────────┤
│ k8s.io/kubernetes │ CVE-2025-5187 │ MEDIUM   │ fixed  │ v1.33.2           │ 1.31.12, 1.32.8, 1.33.4 │ Kubernetes Nodes can delete themselves by adding an │
│                   │               │          │        │                   │                         │ OwnerReference                                      │
│                   │               │          │        │                   │                         │ https://avd.aquasec.com/nvd/cve-2025-5187           │
└───────────────────┴───────────────┴──────────┴────────┴───────────────────┴─────────────────────────┴─────────────────────────────────────────────────────┘

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

[k8s-infra-cherrypick-robot]

@andyzhangx: #2150 failed to apply on top of branch "release-1.26":

Applying: fix: CVE-2025-5187
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	vendor/k8s.io/component-helpers/resource/helpers.go
M	vendor/k8s.io/kubernetes/test/utils/image/manifest.go
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
CONFLICT (content): Merge conflict in vendor/modules.txt
Auto-merging vendor/k8s.io/kubernetes/test/utils/image/manifest.go
CONFLICT (content): Merge conflict in vendor/k8s.io/kubernetes/test/utils/image/manifest.go
Auto-merging vendor/k8s.io/component-helpers/resource/helpers.go
CONFLICT (content): Merge conflict in vendor/k8s.io/component-helpers/resource/helpers.go
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 fix: CVE-2025-5187

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.