CVE-2025-47914 found in golang/golang.org/x/crypto@v0.44.0
CVE-2025-47914 found in golang/golang.org/x/crypto@v0.44.0
Important
Risk: 1.22 (Low)
CVSS: 5.3
Description
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.
Affected component
The vulnerability is in pkg:golang/golang.org/x/crypto@v0.44.0, found in artifacts pkg:devguard/test-org/test-repository.
Recommended fix
Upgrade to version v0.45.0 or later.
# Update all golang packages
go get -u ./...
# Update only this package
go get crypto@v0.45.0 Additional guidance for mitigating vulnerabilities
Visit our guides on devguard.org
See more details...
Path to component
%%{init: { 'theme':'base', 'themeVariables': {
'primaryColor': '#F3F3F3',
'primaryTextColor': '#0D1117',
'primaryBorderColor': '#999999',
'lineColor': '#999999',
'secondaryColor': '#ffffff',
'tertiaryColor': '#ffffff'
} }}%%
flowchart TD
root(["root"]) --- sbom_SBOM_DEFAULT(["sbom:SBOM_DEFAULT"])
sbom_SBOM_DEFAULT(["sbom:SBOM_DEFAULT"]) --- golang_org_x_crypto(["golang.org/x/crypto"])
classDef default stroke-width:2px| Risk Factor | Value | Description |
|---|---|---|
| Vulnerability Depth | 2 |
The vulnerability is in a dependency of a dependency in your project. It is 2 levels deep. |
| EPSS | 0.04 % |
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days. |
| EXPLOIT | Not available |
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database. There are no script kiddies exploiting this vulnerability. |
| CVSS-BE | 5.3 |
|
| CVSS-B | 5.3 |
- The vulnerability can be exploited over the network without needing physical access. - It is easy for an attacker to exploit this vulnerability. - An attacker does not need any special privileges or access rights. - No user interaction is needed for the attacker to exploit this vulnerability. - The impact is confined to the system where the vulnerability exists. - There is a low impact on the availability of the system. |
More details can be found in DevGuard
Interact with this vulnerability
You can use the following slash commands to interact with this vulnerability:
👍 Reply with this to acknowledge and accept the identified risk.
/accept I accept the risk of this vulnerability, because ...
⚠️ Mark the risk as false positive: Use one of these commands if you believe the reported vulnerability is not actually a valid issue.
/component-not-present The vulnerable component is not included in the artifact./vulnerable-code-not-present The component is present, but the vulnerable code is not included or compiled./vulnerable-code-not-in-execute-path The vulnerable code exists, but is never executed at runtime./vulnerable-code-cannot-be-controlled-by-adversary Built-in protections prevent exploitation of this vulnerability./inline-mitigations-already-exist The vulnerable code cannot be controlled or influenced by an attacker.
🔁 Reopen the risk: Use this command to reopen a previously closed or accepted vulnerability.
/reopen ...