resolve CVE within trivy scan

[nathanlaceyraft]

If you do docker build the image and do

trivy image --scanners vuln --ignore-unfixed {image}

You'll get
usr/bin/yq (gobinary)

Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 1, CRITICAL: 0)

┌─────────┬────────────────┬──────────┬────────┬───────────────────┬──────────────────────────────┬────────────────────────────────────────────────────────────┐
│ Library │ Vulnerability │ Severity │ Status │ Installed Version │ Fixed Version │ Title │
├─────────┼────────────────┼──────────┼────────┼───────────────────┼──────────────────────────────┼────────────────────────────────────────────────────────────┤
│ stdlib │ CVE-2025-68121 │ HIGH │ fixed │ v1.25.6 │ 1.24.13, 1.25.7, 1.26.0-rc.3 │ During session resumption in crypto/tls, if the underlying │
│ │ │ │ │ │ │ Config has ...... │
│ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2025-68121 │

Updating to go 1.25.7 resolves the CVE shown in trivy
Thanks for your consideration.

[nathanlaceyraft]

If you merge this PR, you can delete https://github.com/mikefarah/yq/pull/2598/changes which tried to update you to a release candidate.

[nathanlaceyraft]

merging #2603 will also resolve the issue, thanks

[nathanlaceyraft]

cve resolved by merging #2603