🌱 Bump golang.org/x/crypto from 0.48.0 to 0.52.0#987
Conversation
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.48.0 to 0.52.0. - [Commits](golang/crypto@v0.48.0...v0.52.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.52.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
✅ Deploy Preview for ossf-scorecard canceled.
|
Kusari Analysis Results:Caution Flagged Issues Detected The code analysis is clean with zero issues across all categories (no code issues, no exposed secrets, no workflow issues). However, the dependency analysis identifies an active, unmitigated high-severity vulnerability that warrants strong caution before merging. While this PR is a net security improvement — resolving 13+ vulnerabilities in older golang.org/x/crypto and several in golang.org/x/net — the newly introduced golang.org/x/net v0.54.0 carries CVE-2026-39821 (CVSS: AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H), an IDNA privilege escalation flaw where ToASCII/ToUnicode incorrectly accepts Punycode-encoded labels that resolve to ASCII-only hostnames (e.g., 'xn--example-.com' resolving to 'example.com'). This can be exploited by low-privileged network attackers to bypass hostname-based access controls, with high confidentiality and integrity impact and a Changed scope. The vulnerability is not cleared by govulncheck and a direct fix is available. We strongly recommend updating golang.org/x/net to v0.57.0 before merging. Action item: run 'go get golang.org/x/net@v0.57.0', verify go.mod and go.sum are consistent, and confirm no new vulnerabilities or build incompatibilities are introduced by the transitive upgrade. Note View full detailed analysis result for more information on the output and the checks that were run. Required Dependency Mitigations
Summary: The golang.org/x/net/idna package (ToASCII/ToUnicode) incorrectly accepts Punycode-encoded labels that decode to ASCII-only labels (e.g., 'xn--example-.com' resolves to 'example.com'). This can enable privilege escalation in applications performing hostname-based access control. CVSS: AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N Dependency path: golang.org/x/net@v0.54.0 is pulled in via multiple roots:
Fix: Update golang.org/x/net to v0.57.0 which resolves this vulnerability. Note: Upgrading to v0.57.0 may transitively bump other golang.org/x/* packages. Verify the resulting go.mod does not introduce build incompatibilities or new vulnerabilities.
Found this helpful? Give it a 👍 or 👎 reaction! |
Bumps golang.org/x/crypto from 0.48.0 to 0.52.0.
Commits
a1c0d99go.mod: update golang.org/x dependencies3c7c869ssh: fix deadlock on unexpected channel responses533fb3fssh: fix source-address critical option bypassabbc44dssh: fix incorrect operator ordere052873ssh: fix infinite loop on large channel writes due to integer overflowb61cf85ssh: enforce user presence verification for security keys9c2cd33ssh: enforce strict limits on DSA key parameters8907318ssh: reject RSA keys with excessively large moduliffd87b4ssh: fix panic when authority callbacks are nil4e7a738ssh: fix deadlock on unexpected global responsesDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.