Skip to content

fix(cve): GO-2026-5019/GO-2026-5018 - update golang.org/x/crypto v0.50.0 → v0.52.0#3451

Merged
tekton-robot merged 1 commit into
mainfrom
fix/GO-2026-5019-x-crypto-main-attempt-1
May 28, 2026
Merged

fix(cve): GO-2026-5019/GO-2026-5018 - update golang.org/x/crypto v0.50.0 → v0.52.0#3451
tekton-robot merged 1 commit into
mainfrom
fix/GO-2026-5019-x-crypto-main-attempt-1

Conversation

@jkhelil
Copy link
Copy Markdown
Member

@jkhelil jkhelil commented May 28, 2026

CVE Details

Field Value
GO Advisory GO-2026-5019, GO-2026-5018
Package golang.org/x/crypto/ssh
Current Version v0.50.0
Fixed Version v0.52.0

GO-2026-5019: Bypass of FIDO/U2F security keys physical interaction in golang.org/x/crypto/ssh
GO-2026-5018: Pathological RSA/DSA parameters may cause DoS in golang.org/x/crypto/ssh

Fix Summary

  • Update golang.org/x/crypto from v0.50.0 to v0.52.0
  • Also updates golang.org/x/net v0.53.0 → v0.54.0 as transitive dependency
  • Run go mod tidy && go mod verify && go mod vendor

Test Results

Tests passed

Command: go test -short -count=1 ./pkg/... ./cmd/...
Status: PASSED - all 30 packages passed

Breaking Changes

None. This is a patch-level dependency update to indirect dependencies.

Verification Steps

  • Review go.mod and go.sum changes
  • Review vendor/ directory changes for golang.org/x/crypto and golang.org/x/net
  • Run full test suite in CI
  • Confirm govulncheck reports no remaining GO-2026-5019/GO-2026-5018 findings

Risk Assessment

Low — patch-level update to indirect dependencies with no API changes. Tests pass locally.


🤖 Automated fix by CVE Fixer Bot

…0.0 → v0.52.0

- Update golang.org/x/crypto from v0.50.0 to v0.52.0
- Fixes GO-2026-5019: bypass of FIDO/U2F security keys physical interaction in ssh
- Fixes GO-2026-5018: pathological RSA/DSA parameters may cause DoS in ssh
- Also updates golang.org/x/net v0.53.0 → v0.54.0 as transitive dependency

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@tekton-robot tekton-robot requested review from khrm and pramodbindal May 28, 2026 06:16
@tekton-robot tekton-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels May 28, 2026
@jkhelil
Copy link
Copy Markdown
Member Author

jkhelil commented May 28, 2026

/release-note-none

@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels May 28, 2026
@jkhelil
Copy link
Copy Markdown
Member Author

jkhelil commented May 28, 2026

/approve

@jkhelil
Copy link
Copy Markdown
Member Author

jkhelil commented May 28, 2026

/lgtm

@tekton-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkhelil

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 28, 2026
@tekton-robot
Copy link
Copy Markdown
Contributor

@jkhelil: you cannot LGTM your own PR.

Details

In response to this:

/lgtm

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/test-infra repository.

@anithapriyanatarajan
Copy link
Copy Markdown
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label May 28, 2026
@tekton-robot tekton-robot merged commit e363e1a into main May 28, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants