GO-2025-4116

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

High highest severity reported · also known as CVE-2025-47913

5
catalog tools match this advisory
2
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog
0.7%
EPSS for CVE-2025-47913, percentile 52

Catalog tools matching GO-2025-4116

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
gitleaks
Pre-commit & Secrets Detection
v8.30.1golang.org/x/crypto@v0.35.0
golang
0.43.0vulnerable code in binarygo.modDispute
notation
Artifact Signing & Verification
v1.3.2golang.org/x/crypto@v0.37.0
golang
0.43.0vulnerable code in binarygo.modDispute
tracee
Container Security › Runtime Security
v0.24.1golang.org/x/crypto@v0.40.0
golang
0.43.0module in binarygo.modDispute
dockle
Container Security › Image Scanning
v0.4.15golang.org/x/crypto@v0.29.0
golang
0.43.0not in released binarygo.modDispute
slsa-verifier
Supply Chain Compliance
v2.7.1golang.org/x/crypto@v0.36.0
golang
0.43.0module in binarygo.modDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

Go vulnerability GO-2025-4116 · NVD CVE-2025-47913 · OSV GO-2025-4116

Grype data sources: https://go.dev/cl/700295