Skip to content

Fix CVE-2026-39834: bump golang.org/x/crypto to v0.52.0 - #442

Merged
raghavendra-nataraj merged 1 commit into
mainfrom
fix/cve-2026-39834-xcrypto
Jul 20, 2026
Merged

Fix CVE-2026-39834: bump golang.org/x/crypto to v0.52.0#442
raghavendra-nataraj merged 1 commit into
mainfrom
fix/cve-2026-39834-xcrypto

Conversation

@raghavendra-nataraj

Copy link
Copy Markdown
Contributor

What

Bump golang.org/x/crypto from the replace-pinned v0.37.0 to v0.52.0 to remediate CVE-2026-39834 (Critical) — an infinite loop in x/crypto/ssh on Write payloads > 4GB.

Because x/crypto is pinned via a replace directive (which overrides require and is not inherited by downstream modules), the fix must be applied in this repo directly. x/crypto v0.52.0 raises the module-graph minimums for x/net/x/sys, so their replace pins are aligned to v0.54.0/v0.45.0 to keep require==replace==effective.

Verification

  • go list -m golang.org/x/crypto -> v0.52.0 (effective)
  • go mod tidy clean, go build ./... passes
  • (Pre-existing, unrelated) go vet flags a malformed struct tag in pkg/config/config_test.go — not touched by this PR.

Root of the MOC CG remediation chain

This is Step 1 (root moc) of the multi-repo x/crypto remediation; downstream repos (moc-pkg, SDKs, agents, moccli) get their own x/crypto replace bumps.

Work item: AB#38721692

golang.org/x/crypto < v0.52.0 is vulnerable to an infinite loop in the
ssh package on Write payloads larger than 4GB (CVE-2026-39834, Critical).
This repo pins x/crypto via a replace directive, so bump the replace (and
the transitively-required x/net/x/sys replaces that x/crypto v0.52.0 now
demands) to v0.52.0/v0.54.0/v0.45.0 so require==replace==effective.

Work item: AB#38721692

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 4a902de7-e15e-494c-b590-1f9e94a5fadd
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@raghavendra-nataraj

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

@raghavendra-nataraj
raghavendra-nataraj merged commit 3ebd142 into main Jul 20, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants