GO-2026-4918
When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.
Catalog tools matching GO-2026-4918
| Tool | Version scanned | Package | Fixed in | Released binary | Declared in or found in | Dispute |
|---|---|---|---|---|---|---|
| tracee Container Security › Runtime Security | v0.24.1 | golang.org/x/net@v0.38.0golang | 0.53.0 | vulnerable code in binary | cmd/traceectl/go.mod | Dispute |
| tracee Container Security › Runtime Security | v0.24.1 | golang.org/x/net@v0.42.0golang | 0.53.0 | vulnerable code in binary | go.mod | Dispute |
| bomber Software Composition Analysis (SCA) | v0.5.1 | golang.org/x/net@v0.29.0golang | 0.53.0 | vulnerable code in binary | go.mod | Dispute |
| gitleaks Pre-commit & Secrets Detection | v8.30.1 | stdlib@v1.24.11golang | v1.25.10 | vulnerable code in binary | gitleaks (release binary; govulncheck only) | Dispute |
| dockle Container Security › Image Scanning | v0.4.15 | stdlib@v1.22.10golang | v1.25.10 | vulnerable code in binary | dockle (release binary; govulncheck only) | Dispute |
| notation Artifact Signing & Verification | v1.3.2 | stdlib@v1.23.8golang | v1.25.10 | vulnerable code in binary | notation (release binary; govulncheck only) | Dispute |
| gatekeeper Policy as Code | v3.23.1 | stdlib@v1.26.0golang | v1.26.3 | vulnerable code in binary | gator (release binary; govulncheck only) | Dispute |
| clair Container Security › Image Scanning | v4.9.0 | golang.org/x/net@v0.47.0golang | 0.53.0 | vulnerable code in binary | go.mod | Dispute |
| vet Software Composition Analysis (SCA) | v1.20.0 | stdlib@v1.26.2golang | v1.26.3 | vulnerable code in binary | vet (release binary; govulncheck only) | Dispute |
| slsa-verifier Supply Chain Compliance | v2.7.1 | golang.org/x/net@v0.38.0golang | 0.53.0 | vulnerable code in binary | go.mod | Dispute |
| kube-linter Kubernetes Security | v0.8.3 | golang.org/x/net@v0.48.0golang | 0.53.0 | vulnerable code in binary | go.mod | Dispute |
| kube-linter Kubernetes Security | v0.8.3 | golang.org/x/net@v0.50.0golang | 0.53.0 | vulnerable code in binary | tool-imports/go.mod | Dispute |
| talisman Pre-commit & Secrets Detection | v1.37.0 | stdlib@v1.24.2golang | v1.25.10 | vulnerable code in binary | talisman_linux_amd64 (release binary; govulncheck only) | Dispute |
| dive Container Security › Image Scanning | v0.13.1 | golang.org/x/net@v0.37.0golang | 0.53.0 | vulnerable code 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-4918 · NVD CVE-2026-33814 · OSV GO-2026-4918
Grype data sources: https://go.dev/cl/761581 · https://pkg.go.dev/vuln/GO-2026-4918