chore(deps): update module golang.org/x/crypto to v0.45.0 [security] #303
+21
−21
Conversation
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
renovate-sh-app
bot
requested review from
iwysiu and
njvrzm
and removed request for
a team
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate-sh-app
bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
from
3f8615a to
95555fc
Compare
renovate-sh-app
bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
from
95555fc to
256fec6
Compare
renovate-sh-app
bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
2 times, most recently
from
fb6c802 to
27e83a3
Compare
renovate-sh-app
bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
2 times, most recently
from
79a65bb to
6724306
Compare
renovate-sh-app
bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
3 times, most recently
from
9ce482a to
5f16050
Compare
renovate-sh-app
bot
changed the title
auto-merge was automatically disabled
December 24, 2025 15:37
Pull request was closed
renovate-sh-app
bot
deleted the
renovate/go-golang.org-x-crypto-vulnerability
branch
renovate-sh-app
bot
changed the title
renovate-sh-app
bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
from
6f77a7b to
5f16050
Compare
renovate-sh-app
bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
from
5f16050 to
6f77a7b
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate-sh-app
bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
3 times, most recently
from
f130b85 to
d9050de
Compare
| datasource | package | from | to | | ---------- | ------------------- | ------- | ------- | | go | golang.org/x/crypto | v0.43.0 | v0.45.0 | Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
renovate-sh-app
bot
force-pushed
the
renovate/go-golang.org-x-crypto-vulnerability
branch
from
d9050de to
a344b7a
Compare
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.43.0→v0.45.0GitHub Vulnerability Alerts
CVE-2025-58181
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.
CVE-2025-47914
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.
golang.org/x/crypto/ssh allows an attacker to cause unbounded memory consumption
CVE-2025-58181 / GHSA-j5w8-q4qc-rx2x / GO-2025-4134
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 OSV and 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 / GO-2025-4135
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 OSV and the GitHub Advisory Database (CC-BY 4.0).
Malformed constraint may cause denial of service in golang.org/x/crypto/ssh/agent
CVE-2025-47914 / GHSA-f6x5-jh6r-wrfv / GO-2025-4135
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
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Unbounded memory consumption in golang.org/x/crypto/ssh
CVE-2025-58181 / GHSA-j5w8-q4qc-rx2x / GO-2025-4134
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
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 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.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.