GHSA-j5w8-q4qc-rx2x
golang.org/x/crypto/ssh allows an attacker to cause unbounded memory consumption
Catalog tools matching GHSA-j5w8-q4qc-rx2x
| Tool | Version scanned | Package | Fixed in | Released binary | Declared in or found in | Dispute |
|---|---|---|---|---|---|---|
| gitleaks Pre-commit & Secrets Detection | v8.30.1 | golang.org/x/crypto@v0.35.0golang | 0.45.0 | vulnerable code in binary | go.mod | Dispute |
| notation Artifact Signing & Verification | v1.3.2 | golang.org/x/crypto@v0.37.0golang | 0.45.0 | vulnerable code in binary | go.mod | Dispute |
| tracee Container Security › Runtime Security | v0.24.1 | golang.org/x/crypto@v0.40.0golang | 0.45.0 | module in binary | go.mod | Dispute |
| dockle Container Security › Image Scanning | v0.4.15 | golang.org/x/crypto@v0.29.0golang | 0.45.0 | not in released binary | go.mod | Dispute |
| slsa-verifier Supply Chain Compliance | v2.7.1 | golang.org/x/crypto@v0.36.0golang | 0.45.0 | package in binary | go.mod | Dispute |
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
GitHub advisory GHSA-j5w8-q4qc-rx2x · NVD CVE-2025-58181 · OSV GHSA-j5w8-q4qc-rx2x
Grype data sources: https://github.com/advisories/GHSA-j5w8-q4qc-rx2x