Update module golang.org/x/crypto to v0.45.0 [SECURITY] - autoclosed#4231
Closed
renovate[bot] wants to merge 1 commit into
Closed
Update module golang.org/x/crypto to v0.45.0 [SECURITY] - autoclosed#4231renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: flow/pkg/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
❌ 2 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Contributor
🔄 Flaky Test DetectedAnalysis: The sole failure is a PostgreSQL connection being forcibly terminated by an admin shutdown (SQLSTATE 57P01) during a long-running e2e test, a transient infrastructure issue unrelated to the Next.js security update in this PR. ✅ Automatically retrying the workflow |
Contributor
🔄 Flaky Test DetectedAnalysis: A Docker service container (likely the MySQL or Elasticsearch service for the mysql-gtid test matrix) failed to start during CI initialization before any tests ran, which is a transient infrastructure failure unrelated to code changes. ✅ Automatically retrying the workflow |
Contributor
🔄 Flaky Test DetectedAnalysis: The e2e test ✅ Automatically retrying the workflow |
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
from
75de50a to
9cb2617
Compare
Contributor
🔄 Flaky Test DetectedAnalysis: Both failures are caused by ✅ Automatically retrying the workflow |
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
from
9cb2617 to
ecc75ab
Compare
renovate
Bot
changed the title
auto-merge was automatically disabled
April 27, 2026 17:49
Pull request was closed
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
2 times, most recently
from
ecc75ab to
0a0fb33
Compare
Contributor
🔄 Flaky Test DetectedAnalysis: Three unrelated e2e tests failed across different CI matrix jobs due to transient infrastructure issues: a PostgreSQL catalog connection was killed by an admin command (SQLSTATE 57P01), a BigQuery snapshot timed out waiting for async status, and a MongoDB table-addition sequence stalled mid-WaitFor — none of which are related to the triggering commit (a GitHub Actions digest bump). ✅ Automatically retrying the workflow |
Contributor
🔄 Flaky Test DetectedAnalysis: The e2e test ✅ Automatically retrying the workflow |
Contributor
🔄 Flaky Test DetectedAnalysis: TestGenericBQ/Test_Simple_Flow failed with a snapshot status timeout (UNEXPECTED STATUS TIMEOUT STATUS_SNAPSHOT), indicating transient BigQuery API latency or CI runner resource contention rather than a code regression. ✅ Automatically retrying the workflow |
Contributor
🔄 Flaky Test DetectedAnalysis: Test_Binary_Format_Raw failed during teardown because a concurrent test killed its catalog connection (SQLSTATE 57P01: administrator command) and left a replication slot still active (SQLSTATE 55006), both race conditions caused by running 32 e2e tests in parallel. ✅ Automatically retrying the workflow |
Contributor
🔄 Flaky Test DetectedAnalysis: The e2e test suite timed out at exactly the 900s limit on the MariaDB 8.0 CI matrix variant, indicating transient slowness (CDC lag, infrastructure latency, or slow DB startup) rather than a code regression. ✅ Automatically retrying the workflow |
renovate
Bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.42.0→v0.45.0golang.org/x/crypto/ssh allows an attacker to cause unbounded memory consumption
CVE-2025-58181 / GHSA-j5w8-q4qc-rx2x
More information
Details
SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
golang.org/x/crypto/ssh/agent vulnerable to panic if message is malformed due to out of bounds read
CVE-2025-47914 / GHSA-f6x5-jh6r-wrfv
More information
Details
SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: (in timezone Etc/UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.