GO-2026-6354
Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time, handlePacket
Catalog tools matching GO-2026-6354
| Tool | Version scanned | Package | Fixed in | Released binary | Declared in or found in | Dispute |
|---|---|---|---|---|---|---|
| sops Secret Management | v3.13.3 | golang.org/x/crypto@v0.54.0golang | 0.56.0 | vulnerable code in binary | go.mod | Dispute |
| gitleaks Pre-commit & Secrets Detection | v8.30.1 | golang.org/x/crypto@v0.35.0golang | 0.56.0 | vulnerable code in binary | go.mod | Dispute |
| notation Artifact Signing & Verification | v1.3.2 | golang.org/x/crypto@v0.37.0golang | 0.56.0 | vulnerable code in binary | go.mod | Dispute |
| nuclei API & Dynamic Testing (DAST) | v3.11.1 | golang.org/x/crypto@v0.53.0golang | 0.56.0 | vulnerable code in binary | go.mod | Dispute |
| clair Container Security › Image Scanning | v4.9.0 | golang.org/x/crypto@v0.45.0golang | 0.56.0 | vulnerable code in binary | go.mod | Dispute |
| vet Software Composition Analysis (SCA) | v1.20.0 | golang.org/x/crypto@v0.55.0golang | 0.56.0 | vulnerable code in binary | go.mod | Dispute |
| kube-linter Kubernetes Security | v0.8.3 | golang.org/x/crypto@v0.46.0golang | 0.56.0 | vulnerable code in binary | go.mod | Dispute |
| kube-linter Kubernetes Security | v0.8.3 | golang.org/x/crypto@v0.48.0golang | 0.56.0 | vulnerable code in binary | tool-imports/go.mod | Dispute |
| steampipe Cloud Security | v2.4.9 | golang.org/x/crypto@v0.55.0golang | 0.56.0 | vulnerable code in binary | go.mod | Dispute |
| tracee Container Security › Runtime Security | v0.24.1 | golang.org/x/crypto@v0.40.0golang | 0.56.0 | module in binary | go.mod | Dispute |
| dockle Container Security › Image Scanning | v0.4.15 | golang.org/x/crypto@v0.29.0golang | 0.56.0 | not in released binary | go.mod | Dispute |
| infisical Secret Management | v0.167.4 | golang.org/x/crypto@v0.53.0golang | 0.56.0 | not analyzed | backend-go/go.mod | Dispute |
| gatekeeper Policy as Code | v3.23.1 | golang.org/x/crypto@v0.53.0golang | 0.56.0 | module in binary | go.mod | Dispute |
| slsa-verifier Supply Chain Compliance | v2.7.1 | golang.org/x/crypto@v0.36.0golang | 0.56.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
Go vulnerability GO-2026-6354 · NVD CVE-2026-78662 · OSV GO-2026-6354
Grype data sources: https://go.dev/issue/81316