chore(deps): upgrade golang.org/x/crypto, mod, and text past known vulnerabilities #620
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!620
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/bump-x-crypto-mod-text"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
A lockfile-level osv-scanner scan (
--no-call-analysis=all) found 7 known vulnerabilities ingo.mod: GO-2026-5932, -6303, -6354, and -6355 ingolang.org/x/cryptov0.52.0; GO-2026-6179 and -6180 ingolang.org/x/modv0.35.0; and GO-2026-5970 ingolang.org/x/textv0.37.0. madtea does not reach them, which is why govulncheck reports nothing, but they ship in the build.This upgrades
x/cryptoto v0.57.0,x/modto v0.41.0, andx/textto v0.42.0.x/sync,x/sys,x/term,x/tools, andx/netmove up with them. Every change is an upgrade.THIRD-PARTY-LICENSES.mdrecords the new versions; all are BSD-3-Clause.After the upgrade the scan reports one finding: GO-2026-5932 in
x/crypto, which has no fixed version yet. The gate is green.Refs #587