Release new version that uses updated golang version to address known stdlib vulns

[keviny22]

Eschewed features

• This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature.

What would you like to have added?

Current version has the below vulns

`
stdlib

CVE-2025-22874

CVE-2025-47907

CVE-2025-58183

CVE-2025-61726

CVE-2025-61728

CVE-2025-61729
`

Why is this needed?

To address vulns

Can you accomplish the motivating task without this feature, and if so, how?

yes

What other solutions have you considered?

building off of master

Anything else we should know?

No response

Feature ownership

• I am interested in contributing this feature myself! 🎉

[koba1t]

I already know.

/triage accepted
/priority important-longterm

[nXtCyberNet]

Hi, I came across this issue and would like to work on it .Could you please assign this issue to me?

[nXtCyberNet]

/assign

[mattsanta]

Should upgrade go versions again before creating the new release since the newer go versions were published to address more vulns: https://go.dev/doc/devel/release

examples:
https://pkg.go.dev/vuln/GO-2026-4601
https://pkg.go.dev/vuln/GO-2026-4603
https://pkg.go.dev/vuln/GO-2026-4602

[menahyouyeah]

There were more vulns published recently that are fixed with upgrading to Go version 1.25.9. Examples:

CVE-2026-27143
CVE-2026-27144