CVE-2026-78662 (High) detected in golang.org/x/crypto-v0.49.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
Research direction
Start with engine/go.mod and inspect the golang.org/x/crypto dependency currently resolved at v0.49.0. Update it to the stated fixed version, v0.56.0, then run the project's Go checks. Done means the dependency resolves to the fixed version and the checks pass.
Written by the indexing model from the issue text.
Description
CVE-2026-78662 - High Severity Vulnerability
Vulnerable Library - golang.org/x/crypto-v0.49.0
Library home page: https://proxy.golang.org/golang.org/x/crypto/@v/v0.49.0.zip
Sample Path to Dependency File: /engine/go.mod
Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/golang.org/x/crypto/@v/v0.49.0.mod
Dependency Hierarchy:
- ❌ golang.org/x/crypto-v0.49.0 (Vulnerable Library)
Found in base branch: master
Vulnerability Details
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 drops every packet other than the open confirmation/failure, without blocking and without tearing down the connection.
Publish Date: 2026-09-02
URL: CVE-2026-78662
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
Suggested Fix
Type: Upgrade version
Origin: https://pkg.go.dev/vuln/GO-2026-6354
Release Date: 2026-09-02
Fix Resolution: golang.org/x/crypto - v0.56.0,https://github.com/golang/crypto.git - v0.56.0
Step up your Open Source Security Game with Mend here
- Dominant language
- Go
- Stars
- 2.7k
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from postgres-ai/database-lab-engine
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Mend: dependency security vulnerability
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in postgres-ai/database-lab-engine
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·